Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory-plugins fusiondirectory-plugins
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 63
    • Issues 63
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectory-pluginsfusiondirectory-plugins
  • Wiki
  • UserReminder

UserReminder · Changes

Page history
Update UserReminder authored Oct 30, 2017 by bmortier's avatar bmortier
Show whitespace changes
Inline Side-by-side
UserReminder.md
View page @ 4971dc09
...@@ -13,7 +13,7 @@ The email is sent before expiration, with an alert delay which can be configured ...@@ -13,7 +13,7 @@ The email is sent before expiration, with an alert delay which can be configured
There may be some kind of conflict when people are using both shadowExpire, ppolicy and user-reminder. There may be some kind of conflict when people are using both shadowExpire, ppolicy and user-reminder.
### ### Issues
1. In posix mode we look for **shadowExpire** and compare it with the actual date to find if its expired. If not expired we sent an alter to the user if not already send 1. In posix mode we look for **shadowExpire** and compare it with the actual date to find if its expired. If not expired we sent an alter to the user if not already send
...@@ -21,6 +21,7 @@ There may be some kind of conflict when people are using both shadowExpire, ppol ...@@ -21,6 +21,7 @@ There may be some kind of conflict when people are using both shadowExpire, ppol
If we need different pwdMaxAge values in the policies, we need to look at the **pwdPolicySubentry** attribute for the user(s) who are going to be expired. If we need different pwdMaxAge values in the policies, we need to look at the **pwdPolicySubentry** attribute for the user(s) who are going to be expired.
### solution ### Solution
In this case we may want to have an option to trigger user-reminder only on shadow expire or on ppolicy, or to send a different email depending on which expiration it happening. Add a bolean in the interface use ppolicy because posix is the default settings.
\ No newline at end of file Add a box for **Alert message for ppolicy**
Clone repository
  • FusiondirectoryIPAM
  • LSC
  • LdapAlias
  • Modifying group member types
  • RestWebservice
    • addUpdateUser
    • addUpdateUserMultivaluated
    • createUser
    • deleteUser
  • SupannSupport
  • UserReminder
  • deployment features
  • fd lsc backend
  • fd lsc zimbra
  • filters acl
View All Pages