I’m working on a Laravel application that connects with Atlassian products such as Jira and Confluence using their REST APIs. I recently learned about Atlassian Guard and want to understand how it affects integrations from custom apps like Laravel.
Specifically, I’d like to know:
Does Atlassian Guard restrict or modify how API tokens and authentication work for external apps?
How can I ensure my Laravel app follows Atlassian Guard’s security and compliance policies?
Are there best practices for securely managing user credentials, API tokens, and permissions when connecting from Laravel?
Any official documentation or configuration examples would be very helpful.
Hi @Emira Welcome to Atlassian Community!
If you’re looking to access Jira and Confluence data via REST API, you’ll first need an account that has access to the respective Jira projects and Confluence spaces, along with an active license for both products.
Typically, a service account is used for such integrations. You can use a service account that already has access to Jira and Confluence.
You can make API requests using an API token — generate a scoped API token under the service account and use the service account email address along with the token to authenticate your API calls.
Alternatively, you can create an OAuth 2.0 app from developer.atlassian.com to handle authentication and authorization in a more secure way.
Please note that Atlassian Guard (formerly Atlassian Access) is used for enforcing login and authentication policies, configuring SSO (Single Sign-On), and managing user provisioning via SCIM.
https://developer.atlassian.com/cloud/jira/platform/oauth-2-3lo-apps/
https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.