Weave Code
Jira Laravel Package
socialiteproviders/jira
Jira OAuth provider for Laravel Socialite. Add Atlassian Jira login to your Laravel application with this Socialite driver, which handles the OAuth redirect and callback so users can authenticate through Jira with minimal setup. Part of the Socialite Providers collection.
A Collection of Providers for Laravel Socialite
Frequently asked questions about Jira
- How do I install and configure socialiteproviders/jira in Laravel?
- Install it with composer require socialiteproviders/jira, then register the SocialiteProviders Manager SocialiteWasCalled listener in your Laravel app. Add your Atlassian Jira OAuth credentials under services.jira, define a callback route, and call Socialite::driver('jira') to start the flow. The package is a thin Socialite adapter, so no persistence or queue setup is required.
- Which Laravel, PHP, and Socialite versions does socialiteproviders/jira support?
- The expected stack is Laravel with Socialite 5.x and PHP 8.1 or newer, but you must confirm the exact constraints in the tagged composer.json before adopting. The 5.0.0 release notes contain only a compare link, so the PHP floor and illuminate/* and socialite requirements are not documented in the changelog. If 5.0.0 requires a newer framework than you run, treat it as a framework upgrade rather than a package bump.
- What credentials do I need for Jira OAuth login in Laravel?
- You need an Atlassian OAuth 2.0 (3LO) app with a client ID, client secret, and redirect URI that matches your Laravel callback route. Store those values in config/services.php under the jira entry used by Socialite. The provider handles the redirect and callback, but the Atlassian app configuration and scopes remain your responsibility.
- How do I authenticate a user with Socialite::driver('jira')?
- Register the SocialiteWasCalled listener, add the jira service configuration, and create a callback route in Laravel. Redirect users with Socialite::driver('jira')->redirect(), then exchange the callback for a user with Socialite::driver('jira')->user(). The driver returns the authenticated Jira user; persist or map that user in your own application.
- Does socialiteproviders/jira provide access to the Jira REST API?
- No. It authenticates users through Atlassian Jira OAuth and returns a Socialite user, but it does not abstract the Jira REST API. If you need to call Jira, cloudId resolution through accessible-resources and the HTTP client remain your responsibility. Plan for token handling and Jira API routing separately from the login flow.
- What changed in socialiteproviders/jira 5.0.0?
- The 5.0.0 release notes contain only a compare link, with no changelog body or upgrade guide, so the exact changes must be verified from the diff and tagged composer.json. Likely areas to check include raised PHP and illuminate/* or socialite constraints, provider or config key renames, and removal of deprecated AbstractProvider methods. Do not assume the major bump is safe until those constraints and the Manager listener registration are reviewed.
- Is socialiteproviders/jira maintained and safe for production?
- It is a community-org package with an effectively single-maintainer bus factor and a low steady-state maintenance load. That standing risk is not new to 5.0.0, but it means you should pin versions, test upgrades, and keep a rollback path. Validate it in a non-critical environment before relying on it for production Jira login.
- How should I test Jira OAuth login with this Laravel package?
- Use a Jira sandbox tenant and exercise the full flow: login, consent, callback, token exchange, and user fetch. Also test negative paths such as denied consent, expired or replayed state, redirect-URI mismatch, and revoked tokens. Canary the integration in a non-critical environment and keep a composer.lock revert ready for rollback.
- Can I add Jira alongside Google, GitHub, or Okta in an existing Laravel Socialite setup?
- Yes. It slots into an existing Socialite setup as one more driver, one more services entry, and one more callback route. You do not need to replace your current providers or change the overall Socialite flow. Just ensure the SocialiteProviders Manager listener is registered and your Jira callback route is distinct.
- What are the alternatives to socialiteproviders/jira for Jira login in Laravel?
- The main alternative is writing your own Atlassian OAuth 2.0 flow against Socialite or directly with an HTTP client, which gives control but adds bespoke OAuth code to maintain. This package removes that code for the login and callback path, but it still does not handle Jira REST API calls or cloudId resolution. Evaluate it as a thin Socialite adapter, not as a full Jira SDK.
Weaver
How can I help you explore Laravel packages today?