Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "OpenID"

(Requesting a Client ID)
(Replaced content with "Content describing usage of OpenID within Eclipse Foundation has moved, see the new [https://webdev.eclipse.org/docs/api/openid/ Webdev API OpenID page].")
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The Eclipse Foundation provides user authorization from third-part websites and tools using OpenID Connect.
+
Content describing usage of OpenID within Eclipse Foundation has moved, see the new [https://webdev.eclipse.org/docs/api/openid/ Webdev API OpenID page].
 
+
To enable a site or application to leverage a users' Eclipse account, a request must be made to the webdev team.
+
 
+
== Who can request an OpenID Client ID ==
+
# Eclipse Projects who wish to use Eclipse accounts for Eclipse project-related content and applications;
+
# Eclipse Committers who wish to operate services for the Eclipse Community, as approved by the Eclipse Management Organization;
+
# Eclipse Members (Solutions Members and Strategic Members) who wish to operate services for the Eclipse Community, as approved by the Eclipse Management Organization;
+
 
+
 
+
== Revoking a Client ID ==
+
The Eclipse Management Organization (EMO) may, at its discretion, choose to revoke a Client ID at any time. The reasons may include:
+
# Faulty software which generates too many requests to our service;
+
# Abuse of any kind;
+
# Usage for other purposes that are not Eclipse-related.
+
 
+
 
+
== Requesting a Client ID ==
+
To request a client_id and a client_secret, please open a bug under Community > OpenID Connect. Please specify the following:
+
# Your Eclipse-related project or member affiliation;
+
# The purpose of the request (why do you need Eclipse authorization?);
+
# Where this authorization will be used (website, rich client app);
+
# An estimate on how many user authentication/authorization calls per day we can expect to receive.
+
# The callback URL of your application. This is the url where the user should be returned to after signing in.
+
 
+
== Endpoint (URL's) ==
+
 
+
Authorization endpoint:
+
https://accounts.eclipse.org/oauth2/authorize
+
 
+
Token endpoint:
+
https://accounts.eclipse.org/oauth2/token
+
 
+
User information endpoint:
+
https://accounts.eclipse.org/oauth2/UserInfo
+
 
+
== Scope Values ==
+
OpenID Connect Clients use scope values to specify what access privileges are being requested for Access Tokens.
+
 
+
=== openid ===
+
REQUIRED. Informs the Authorization Server that the Client is making an OpenID Connect request. If the openid scope value is not present, the behavior is entirely unspecified.
+
 
+
=== profile ===
+
OPTIONAL. This scope value requests access to the End-User's default profile Claims, which are: name, family_name, given_name, middle_name, nickname, preferred_username, profile, picture, website, gender, birthdate, zoneinfo, locale, and updated_at.
+
 
+
=== email ===
+
OPTIONAL. This scope value requests access to the email and email_verified Claims.
+

Latest revision as of 15:47, 26 February 2024

Content describing usage of OpenID within Eclipse Foundation has moved, see the new Webdev API OpenID page.

Back to the top