search

reTHINK-project / core-framework

The main goal of WP3 is to provide the reTHINK core framework comprised by the runtime environment where Hyperties are executed and the messaging nodes used to support messages exchange between Hyperties.
Apache License 2.0
1 stars 0 forks source link

Domain Login #55

Closed KCorre closed 8 years ago

KCorre commented 9 years ago

@pchainho @jmcrom Concerning the Domain Login dynamic-view diagram -> here

Request initiator

Implicit

As I understand the implicit flow is limited in trust (compared to the Code flow) because the client (the Service Provider) is not authenticated to the IdP. (https://www.scottbrady91.com/OpenID-Connect/OpenID-Connect-Flows) It should then be possible that the Service Provider Backend use the ID Token as some sort of refresh token by authenticating to the IdP. But I think this is not following the OIDC specification.

pchainho commented 9 years ago

The login request should be initiated by the hyperty to the runtime not the other way around

The idea is to be able to share the same domain connection with several Hyperties, if needed. Hyperties would just send messages and the runtime core components would be in charge of resolving and route the message to the appropriate domain. If the domain is not connected yet the core runtime would manage it.