integration guide for eBox HIPs HIP FAS flows Content Documentation of specific OIDC flows This document is an addendum to the OIDC integration guide ID: 1047720
Download Presentation The PPT/PDF document "addendum to the OIDC" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
1. addendum to the OIDC integration guide for eBox HIPsHIP – FAS flows
2. Content : Documentation of specific OIDC flowsThis document is an addendum to the OIDC integration guide for eBox HIPs, it describes 3 flows:Authorization Code Flow - FAS ConsentThis flow must be used by the HIP RP to force the consent page via the FAS user interface during login. The HIP itself does not need to implement the consent page.Authorization Code Flow - HIP Consent (=implicit consent)This flow can be used by the HIP RP to handle the consent page by itself. This flow is not recommended. (note: in all cases the consent itself is stored in FAS)Refresh Token FlowThis flow can be used by the HIP RP to keep a long lasting token for every user. Implementation of this flow is only recommended when the HIP does not use FAS to authenticate each time. (for instance when the HIP manages its own authentication methods outside the FAS, but FAS is only used when a consent is requested)
3. Details of the OpenID Connect calls / responses from and towards the FAS can be found in the FAS OIDC Integration Guide.
4. Details of the OpenID Connect calls / responses from and towards the FAS can be found in the FAS OIDC Integration Guide.
5. Details of the OpenID Connect calls / responses from and towards the FAS can be found in the FAS OIDC Integration Guide.