|= Logging In =
|WFrom the [http://sourceforge.net/account/login.php "log in page"] on !SourceForge.net, there are 2 log in forms - the standard !SourceForge.net account log in form on the left and the OpenID log in form on the right.
|To log in with an OpenID, enter the desired OpenID identifier (URL) into the OpenID input box on the right and click the "Log in" button.
|Users may also select from one of the OpenID provider buttons which will pre-load data for the specified provider.
|We support many other OpenID providers and not all are listed there. Once you have pressed the log in button, users are forwarded to the selected Identity Provider to authenticate and are then returned to the site.
|= New Users =
|New users to !SourceForge.net may log in with OpenID which allows for creation of a !SourceForge.net account.
|Note: Users are required to provide a !SourceForge.net-unique username and password as these credentials are required for non-web services on the site (e.g., Project Web, CVS, SVN, etc.).
|An email will be sent to confirm creation of the new account. Please be sure to complete the account confirmation to get full site services. This is required of all users on !SourceForge.net.
|= Delegation =
|Delegation allows users to use their !SourceForge.net username (i.e., http://sf.net/users/username ) page as a delegation URL for other OpenID sites. A "real" OpenID associated to a !SourceForge.net account is required to enable this feature.
|Once logged into !SourceForge.net, on the [https://sourceforge.net/my/ "My"] page, click on the [https://sourceforge.net/account/ "Account Options"] link. In the section of links note the link [https://sourceforge.net/account/openid.php "Manage My OpenIDs"].
|A !SourceForge.net identity (delegation) for email (!firstname.lastname@example.org), may now be used at other OpenID-enabled sites.
|= FAQ =
|Q: Why doesn't my delegation OpenID work on !SourceForge.net?
|A: Unfortunately, the !SourceForge.net OpenID client does not yet support XRDS or Yadis-based discovery. This is being addressed with ZF. Users can add HTML discovery elements to their delegation page to work for !SourceForge.net. This is a delegation block, for Verisign, verified to work with the existing !SourceForge.net implementation:
|<link rel="openid.server" href="http://pip.verisignlabs.com/server" />
|<link rel="openid.delegate" href="http://username.pip.verisignlabs.com/" />
|<link rel="openid2.provider" href="http://pip.verisignlabs.com/server" />
|<link rel="openid2.local_id" href="http://username.pip.verisignlabs.com/" />
|Q: Why doesn't my i-name work?
|A: The !SourceForge.net ZF OpenID component doesn't fully support XRI & i-name discovery at this time. An issue has been file in the ZF tracker.
|Q: How come all of the fields in account registration aren't pre-populated from my OpenID provider?
|A: During account registration, the number of fields that can be pre-populated is dependent on the ID provider. It might be that all of the fields weren't completed, or the id provider doesn't account for everything (e.g., time zone, language, country, etc.). If these things are not correct, that means the ID providers are not adhering to the specification (registration extension: [http://openid.net/specs/openid-simple-registration-extension-1_0.html "http://openid.net/specs/openid-simple-registration-extension-1_0.html"]).
|Q: What is the deal with http vs. https?
|A: !SourceForge.net follows the specification on this, i.e., normalization: [http://openid.net/specs/openid-authentication-2_0.html#normalization_example "http://openid.net/specs/openid-authentication-2_0.html#normalization_example"]. Hence, an http OpenID is different than an https OpenID. If the selected provider offers both, !SourceForge.net suggests using https. Both may be used, but !SourceForge.net considers them as two separate OpenIDs.