-
Notifications
You must be signed in to change notification settings - Fork 5
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
Use saml entitlement attribute for activation flow #336
Conversation
ac2a939
to
ede11a5
Compare
|
||
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'; |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
e708f59
to
07173a5
Compare
There was a problem hiding this 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.
src/Surfnet/StepupSelfService/SelfServiceBundle/DependencyInjection/Configuration.php
Outdated
Show resolved
Hide resolved
src/Surfnet/StepupSelfService/SelfServiceBundle/Security/Authentication/SamlAuthenticator.php
Show resolved
Hide resolved
src/Surfnet/StepupSelfService/SelfServiceBundle/Security/Authentication/SamlAuthenticator.php
Outdated
Show resolved
Hide resolved
src/Surfnet/StepupSelfService/SelfServiceBundle/Service/ActivationFlowService.php
Outdated
Show resolved
Hide resolved
src/Surfnet/StepupSelfService/SelfServiceBundle/Service/ActivationFlowService.php
Show resolved
Hide resolved
src/Surfnet/StepupSelfService/SelfServiceBundle/Service/ActivationFlowService.php
Outdated
Show resolved
Hide resolved
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
07173a5
to
6b4ed2b
Compare
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