yetangitu/lam
1
0
Fork 0
mirror of https://github.com/LDAPAccountManager/lam.git synced 2025-10-03 17:59:21 +02:00
Code Issues Releases Wiki Activity

#275 2FA login

Browse source
This commit is contained in:
Roland Gruber 2024-02-16 20:45:08 +01:00
parent 190a976ede
commit 24d9a2c662
2 changed files with 5 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

1
lam/HISTORY
View file

@ -5,6 +5,7 @@ March 2024 8.7
-> Cron job to deactivate inactive accounts based on lastBind overlay data (265) -> Cron job to deactivate inactive accounts based on lastBind overlay data (265)
-> Request access: support Windows groups (266) -> Request access: support Windows groups (266)
-> Request access: usability improvements (278, 279) -> Request access: usability improvements (278, 279)
-> Self service: passwordless SSO login supported for Okta and OpenID
- Fixed bugs: - Fixed bugs:
-> User self registration creates accounts only with SSHA hash (287) -> User self registration creates accounts only with SSHA hash (287)

5
lam/docs/manual-sources/chapter-selfService.xml
View file

@ -202,7 +202,10 @@
server is responsible to authenticate your users. LAM will use server is responsible to authenticate your users. LAM will use
the given user name + password for the LDAP login. To setup HTTP the given user name + password for the LDAP login. To setup HTTP
authentication in Apache please see this <ulink authentication in Apache please see this <ulink
url="http://httpd.apache.org/docs/2.2/howto/auth.html">link</ulink>.</entry> url="http://httpd.apache.org/docs/2.2/howto/auth.html">link</ulink>.
If you use Okta or OpenID for 2FA then you can also select to
trust the 2FA provider. In this case the user does not need to
enter any password in LAM itself (SSO).</entry>
</row> </row>
<row> <row>