feat: implement account linking plugin #8091
Conversation
Signed-off-by: jgomer2001 <bonustrack310@gmail.com>
Signed-off-by: jgomer2001 <bonustrack310@gmail.com>
mo-auto
added
area-documentation
|
|
|
||
| In this case, we are populating the configuration of an OAuth-based provider called "Goooogle". | ||
|
|
||
| The tables shown in [this](https://github.com/JanssenProject/jans/blob/main/docs/agama-catalog/jans/inboundID/README.md#supply-configurations) page list all possible properties to configure a provider. Particularly, two properties deserve the most detail: |
There was a problem hiding this comment.
This link should be a https://docs.jans.io . @ossdhaval this has to be added to the mkdocs and then referenced here.
|
|
||
| ## Configuring attribute mappings | ||
|
|
||
| An introduction to attribute mapping can be found [here](https://github.com/JanssenProject/jans/blob/main/docs/agama-catalog/jans/inboundID/README.md#attribute-mappings). Unless an elaborated processing of attributes is required, a basic knowledge of Java language suffices to write a useful mapping. |
There was a problem hiding this comment.
Again the same thing as above
CC @ossdhaval
|
|
||
| This plugin allows users to "link" their local Jans account with existing accounts at third-party identity providers like OIDC OPs and social sites, e.g. Apple, Facebook, Google, etc. | ||
|
|
||
| Besides the usual onboarding of a plugin jar file in Casa, administrators must deploy a number of additional components. This will be regarded later. By now let's summary key points of the accounts linking experience: |
There was a problem hiding this comment.
However, lets summarize the key points of the ....
There was a problem hiding this comment.
Can we just make issues to track the changes to docs so we can start testing?
Signed-off-by: jgomer2001 <bonustrack310@gmail.com>
|
|
|
Prepare
Description
Target issue
closes #7556
Implementation Details
Test and Document the changes