

Please find more details in the documentation linked below: It allows you to create multiple, secure API tokens per user which can be used instead of a user's password, which is not available in an SSO-enabled Atlassian application anymore. Option 1: Use API Token Authentication for Jira, Confluence and Bitbucket (Server & Data Center)įor Jira, Confluence and Bitbucket Server and Data Center, we provide an app called API Token Authentication: However, there are alternative options to authenticate against the REST API when using our SAML SSO app. So it is not possible to log in with your SSO credentials (your username/ password on the Identity Provider) on the REST API via Basic or Bearer Authentication.

This won't work when only using the REST API since the login page is never visited. Enabling SSO redirection only applies to logins using a web browser (see How SAML Single Sign On works).
