Federated authentication for OAuth 2.0(DAPS) extension #2434
-
An OAuth 2.0 application can be configured to work with multiple identity providers, allowing applications to authenticate using different providers. This process is also known as "federated authentication". |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hi, Can you provide more detail? Two connectors from different dataspaces don't communicate with one another. Instead, they need to be part of a common dataspace. A connector can be part of 1..N dataspaces. If a connector is a member of multiple dataspaces, it may need to authenticate or verify identity tokens with multiple providers depending on the current dataspace context. In that case, there should be a mechanism to specify which dataspace and trust anchors are accepted. Is that the use case you are outlining? |
Beta Was this translation helpful? Give feedback.
Hi,
Can you provide more detail? Two connectors from different dataspaces don't communicate with one another. Instead, they need to be part of a common dataspace.
A connector can be part of 1..N dataspaces. If a connector is a member of multiple dataspaces, it may need to authenticate or verify identity tokens with multiple providers depending on the current dataspace context. In that case, there should be a mechanism to specify which dataspace and trust anchors are accepted.
Is that the use case you are outlining?