Medium Hi folks,
Thanks for your feedback and continued support. We wanted to give you an update on the status of this issue.
Over the near term, the direction we're taking with Crowd is to focus on scalability, reliability and performance. We understand the importance of adding additional connectivity to Crowd, however our efforts are will be used to improve scalability and performance. Because of this, significant improvements to our OpenID support are unlikely to occur in the next 12 months. We will continue to re-evaluate and update this issue when we have more information.
Regards,
Eugene Mak
Atlassian Product Management
The CrowdID server currently ignores requests for identifier selection (http://specs.openid.net/auth/2.0/identifier_select). This is also known as "directed identity".
CrowdID should populate the identifier field automatically if the remote user is logged in via SSO. If the user is not logged in, then CrowdID should present the user with a log in screen and then process the authentication request.
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[CWD-1310] Support OpenID 2.0 server-side identifier selection
| Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1511097 ] | New: JAC Bug Workflow v3 [ 3365426 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Simplified Crowd Development Workflow v2 [ 1393157 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1511097 ] |
| Workflow | Original: Crowd Development Workflow v2 [ 271912 ] | New: Simplified Crowd Development Workflow v2 [ 1393157 ] |
| Fix Version/s | New: 2.6 [ 25892 ] | |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Remote Link | New: This issue links to "Wiki Page (Extranet)" [ 25777 ] |
| Assignee | Original: David O'Flynn [Atlassian] [ doflynn ] |
| Labels | New: lt |
Eugene Mak [Atlassian]
made changes -
| Description |
Original:
The CrowdID server currently ignores requests for identifier selection (http://specs.openid.net/auth/2.0/identifier_select). This is also known as "directed identity".
CrowdID should populate the identifier field automatically if the remote user is logged in via SSO. If the user is not logged in, then CrowdID should present the user with a log in screen and then process the authentication request. |
New:
{panel:title=Atlassian Status as of 27 April 2011|borderStyle=solid|borderColor=#3C78B5| titleBGColor=#3C78B5| bgColor=#E7F4FA}
Hi folks, Thanks for your feedback and continued support. We wanted to give you an update on the status of this issue. Over the near term, the direction we're taking with Crowd is to focus on scalability, reliability and performance. We understand the importance of adding additional connectivity to Crowd, however our efforts are will be used to improve scalability and performance. Because of this, significant improvements to our OpenID support are unlikely to occur in the next 12 months. We will continue to re-evaluate and update this issue when we have more information. Regards, Eugene Mak Atlassian Product Management {panel} The CrowdID server currently ignores requests for identifier selection (http://specs.openid.net/auth/2.0/identifier_select). This is also known as "directed identity". CrowdID should populate the identifier field automatically if the remote user is logged in via SSO. If the user is not logged in, then CrowdID should present the user with a log in screen and then process the authentication request. |