forked from IQSS/dataverse
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
- Loading branch information
1 parent
4f1bfea
commit 4779395
Showing
1 changed file
with
16 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
# Basic OpenID Connect support | ||
Working on epic #5974 brought us refactored code for our OAuth 2.0 based login options. | ||
This has now been extended to provide basic support for any OpenID Connect compliant | ||
authentication provider. | ||
|
||
While with our OAuth 2.0 login options you had to implement support for every provider | ||
by pull request, OpenID Connect provides a standardized way for authentication, user | ||
details and more. You are able to use any provider just by loading a configuration file, | ||
without touching the codebase. | ||
|
||
While the usual prominent providers like Google et al feature OIDC support, there are | ||
plenty of options to easily attach your current user storage to a custom made provider, | ||
using enterprise grade software. See documentation for more details. | ||
|
||
This is to be extended with support for attribute mapping, group syncing and more in | ||
future versions of the code. |