Skip to content

Add configuration for fallback GSSP #443

Open
@pmeulen

Description

@pmeulen

The configuration for the fallback GSSP is static and stored in https://github.com/OpenConext/Stepup-Gateway/tree/main/config/openconext

The gateway currently has a dynamic list of GSSPs configured. See for example the azuremfa GSSP configuration in https://github.com/OpenConext/Stepup-Gateway/blob/main/config/openconext/samlstepupproviders.yaml#L51-L70 and the corresponding https://github.com/OpenConext/Stepup-Gateway/blob/main/config/openconext/samlstepupproviders_parameters.yaml.dist#L58-L90 for the parameters.

Does it make sense to reuse this configuration for the fallback GSSP or do we want to add new configuration for this?

If we use the samlstepupproviders.yaml for the configuration then we can reference the GSSP by it's ID parameters.yaml:

Proposed way forward (TODO: discuss):

  • Add the fallback GSSP to the samlstepupproviders.yaml, with possibly a dummy hosted.identity_provider configuration. When the GSSP does double duty as we want to do with AzureMFA, this does not apply.
  • Add the other configuration to the parameters.yml:
    # The GSSP ID from samlstepupproviders.yaml to use as fallback GSSP
    # Set fallback_gssp to false to disable the fallback_gssp functionality
    # fallback_gssp: false
    fallback_gssp: 'azuremfa'

    # The user attribute to use in the Subject of the AuthnRequest to the fallback GSSP
    fallback_gssp_subject_attribute: 'urn:mace:dir:attribute-def:mail'

If the user's institution must be retrieved from an attribute too (see discussion at: #442)

    # The user attribute to use to determine the user's home institution
    fallback_gssp_institution_attribute: 'urn:mace:terena.org:attribute-def:schacHomeOrganization'

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

Status

Delivered

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions