As discussed in https://support.atlassian.com/browse/CWDSUP-4954, some Applications as like Jenkins (formerly known as Hudson) supports OpenId and also OpenId SSO. To make SSO work, you ahve to provide an endpoint URL as like https://www.google.com/accounts/o8/id or https://my.yahoo.com which will work for all users.
This is NOT possible with CrowdId at the moment, because every user has it'S unique URL and using a more generic one without the username suffix, the SSO procedure will stop with a security exception in CrowdId (URL mismatches logged in User)
Please provide a single OpenID Endpoint! It's not handy to tell every domain user what he was to enter when using OpenID with CrowdId ;(
- incorporates
-
CWD-1638 Support form redirect POST communication with OpenID consumer
- Closed
- is duplicated by
-
CWD-1310 Support OpenID 2.0 server-side identifier selection
- Closed
-
CWD-1329 OpenID 2.0 rel attribute should be specified in discovery HTML
- Closed
-
CWD-1666 Facebook interop fails. CrowdId or Facebook to blame?
- Closed
- is related to
-
CWD-2989 OpenID 2.0 and identifier select support
- Closed
-
CWD-3060 Use OpenID Realm for approval requests
- Closed
- Testing discovered
-
CWD-3065 Accept 'GET' requests to the OpenID endpoint
- Closed
-
CWD-3121 Make the OpenID endpoint URL more prominent
- Closed
- mentioned in
-
Wiki Page Loading...