Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use saml entitlement attribute for activation flow #336

Conversation

pablothedude
Copy link
Contributor

@pablothedude pablothedude commented Oct 30, 2024

Use the saml entitlement attribute to allow the activation flow.
If no activation could be allowed this will still result in service
desk vetting.

https://www.pivotaltracker.com/n/projects/1163646/stories/185558419
OpenConext/OpenConext-devconf#17

@pablothedude pablothedude force-pushed the feature/use-entiltlement-saml-attributes-for-activation-flow branch from ac2a939 to ede11a5 Compare October 30, 2024 13:28
@pablothedude pablothedude requested review from MKodde and parijke and removed request for MKodde November 1, 2024 14:26

class ActivationFlowService
{
private const ACTIVATION_FLOW_PREFERENCE_SESSION_NAME = 'self_service_activation_flow_preference';
private const ACTIVATION_FLOW_ENTITLEMENT_SAML_ATTRIBUTE = 'urn:mace:dir:attribute-def:eduPersonEntitlement';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please make this value configurable. We use a different attribute-name for our entitlements

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 for making the name of the entitlement attribute configurable.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've made it configurable

@pablothedude pablothedude force-pushed the feature/use-entiltlement-saml-attributes-for-activation-flow branch from e708f59 to 07173a5 Compare November 5, 2024 13:35
Copy link
Member

@MKodde MKodde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome work. I see the new feature come to live and while at it you repair the damages being done by the introduction of the new SAML Authentcator.

Question: must you not enforce the preference in the activation wizard? When the user is presented how to activate its token. You now also have to consider the preference expressed in the SAML entitlement attribute right?

And see some suggestions below.

Use the saml entitlement attribute to allow the activation flow.
If no activation could be allowed this will still result in service
desk vetting.

Also fixed the handling of imcoming query params which were not handled
correctly because the StepupSamlBundle handles the authentication
and the acivation flow param was therefore lost after entering first on
the consume-assertion endpoint in the application.

https://www.pivotaltracker.com/n/projects/1163646/stories/185558419
@pablothedude pablothedude force-pushed the feature/use-entiltlement-saml-attributes-for-activation-flow branch from 07173a5 to 6b4ed2b Compare November 7, 2024 10:40
@pablothedude pablothedude merged commit 6eca10c into main Nov 11, 2024
2 checks passed
@pablothedude pablothedude deleted the feature/use-entiltlement-saml-attributes-for-activation-flow branch November 11, 2024 09:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants