Add mapping capabilities for OIDC & SAML
Matar Peles
Today we have a static and strict small schema we bring about users and teams when integrating with an identity provider (user names, mails, team names)
The idea here is to have the whole payload coming from the SSO provider (the schema should be known based on the SSO protocol)
and for Port builders to be able to decide what they want to map to the user and team blueprints.
Matan Grady
Travis Gosselin Etienne Jacquot Hadar Basson can you please share a bit more on what type of data you would use this capability to bring into Port?
We are looking to learn more about the use case, the type of data, and the objects associated
E
Etienne Jacquot
Matan Grady the goal is to get additional information for our user coming from our Identity Provider. As an example, we are using a UUID as unique identifier for each of our user. In our systems, it is this UUID that is identifying the users. It helps us to keep the personal information in a secured place and the systems only refer to this UUID.
I would like to be able to add (map) this information in the User blueprint based on the SAML or OIDC information send in the token.
It can also help with data such as "is manager", get the information about hierarchy, team management, ...
T
Travis Gosselin
Matan Grady Our use cases focuses around the import of the teams, to include additional metadata around extending the Team model in port. For example, including additional attributes from the identity provider around the team name, description, manager, and some other custom properties that we would use to map team inheritance to other blueprints.
S
Shlomi Benita
This is super helpful for the GitHub use cases that you have different ID than Email.