You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/stepupsfo.md
+25Lines changed: 25 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,3 +96,28 @@ running the SFO service:
96
96
- The entityid and certificate configured in the authsource above.
97
97
- The namespace of the subjectattribute you're using (likely something like `urn:collab:person:example.org:`).
98
98
- The AssertionConsumerService location: `<your ssp base url>/module.php/stepupsfo/acs.php`.
99
+
100
+
Conditional LOA
101
+
---------------
102
+
103
+
In addition to setting the `loa` setting for the authproc's config, you can also add an extra `loa` attribute to the user's attributes, for instance by adding the attribute to the LDAP or setting it using core:PHP or any other auth proc. You should of course make sure you put this auth proc before your SFO-related auth procs.
The `loa` set in the authproc config is used as the default (optional). The `loa` set in the user's attributes will take precedence. Setting the `loa` to an empty string will skip the SFO. Not setting the `loa` will result in an error.
0 commit comments