175
Customers have installed this add-on in at least 175 active instances.
    by Pawel Niewiadomskifor JIRA Server 7.0.0 - 7.2.6 and more versions
    Versions available for JIRA Server 6.0 - 6.4.14
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Supported
    Pawel Niewiadomski supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.

    Authenticate with Google Apps, Facebook, GitHub or LinkedIn

    Authenticate with Google Apps, Facebook, GitHub or LinkedIn

    Easy sign up

    Easy to use

    Limit to Google Apps

    Users can sign up in seconds with one of their existing account. When using Google Apps you can limit users to a selected domains to make sure no one else will access your instance

    One click sign up and authentication available directly from Login page and Dashboard.

    You can limit Google authentication only to your domain to make sure only your employees have access.

    More details

    There are no additional details.

    User reviews

    (7)
    Sign in to write a review »
    by Bernhard Grünewaldt on 2016-09-13
    Awesome plugin. Works like a charm. Keep up the good work :)
    Was this review helpful?YesNo
    by cPrime Labs on 2016-08-30
    It was easy to install and configure even with lack of documentation (that landing isn't documentation, right?) Generally everything works fine, however websudo requires local password which is extremely confusing for users. If this something configurable or planned to be fixed/improved any time soon?
    Was this review helpful?YesNo
    by Andrey Mischenko on 2016-02-01
    Hello. Do you plan to add option for Google OAuth2 auth parameter prompt? Now prompt always equal to "select_account". But we use restricted domain for auth (Allowed Domains in options) and get parameter prompt with value "none" and parameter hd (hosted domain) will be very useful, because this enable Google Account auto selection with passed domain.
    Was this review helpful?YesNo
    by Dmitry Miroshnichenko on 2015-12-17
    JIRA 7.0.4 google apps integration doesn't work. Logs are clean UPD. I have found the cause. We are using crowd with SSO configured. There is an authentificator in seraph-config.xml <authenticator class="com.atlassian.jira.security.login.SSOSeraphAuthenticator"/> Somehow SSO conflicts with google apps integration. When I try to login with your magic button login count increases but login doesn't happen. We like your plugin and want to use it on our production. But also we want to have SSO. Can you fix this issue please.
    Was this review helpful?YesNo

    Pawel Niewiadomski

    Thanks for feedback. I don't plan to support SSO at this time. Sorry.

    by Ryan Flores on 2015-06-20
    This works just as expected using Google Apps. My only critiques are in regards to the OpenID Login gadget, which from what I can tell is useless. 1) It doesn't make much sense to have an OpenID Login gadget visible when already logged in. 2) When logged out and viewing the System Dashboard, it's a pretty poor UX to display two login gadgets (the built-in JIRA gadget and the OpenID gadget). Why not just customize the built-in Login gadget similar to what's shown on the Login page? 3) Rather than have a dropdown on the Login page, design the page to work similar to how other sites are doing it, like BitBucket, which is a much nicer and cleaner way of presenting the OAuth/OpenID connectors. By making these three adjustments, this will totally provide a richer UX and bridge the gap between JIRA Server and Google Apps Integration that people have been asking for in https://jira.atlassian.com/browse/JRA-21981
    Was this review helpful?YesNo

    Pawel Niewiadomski

    Thanks for feedback.

    1) Totally agree but unfortunately JIRA gadgets are really limited and there's no way to show/hide them if user is authenticated

    2) In JIRA > 6.4.9 plugin will extend JIRA Login gadget directly

    3) Drop down was replaced with a cleaner UI

    Pricing

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications on your instance. For example, if you're running JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for add-ons.

    For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

    Do you offer academic, community, or open-source licenses?

    For server add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server add-ons, you can extend your add-on trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons for my legacy JIRA Server or Confluence Server license?

    If you own a legacy JIRA Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy add-on pricing is no longer available. You have two options for add-on purchasing:

    • Purchase the add-on at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the add-on at the same tier.

    Learn more

    Support

    Pawel Niewiadomski supports OpenID Authentication for JIRA. You can ask a support question via Atlassian Answers to get help.

    Ask a question

    Versions

    Version 3.0.5 JIRA Server 7.0.0 - 7.2.6 Released 2016-10-31

    Summary

    Bug fixes + you can now select a prompt type

    Details

    Better redirection handling to support reverse proxies.

    You can select a prompt type (select account, consent screen or nothing).

    Fixed parsing response from user info URL.

    Installation

    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate OpenID Authentication for JIRA via search. The appropriate add-on version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for OpenID Authentication for JIRA. You're prompted to log into MyAtlassian. OpenID Authentication for JIRA begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your JIRA instance.

    To find older OpenID Authentication for JIRA versions compatible with your instance, you can look through our version history page.

    Similar add-ons