This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Filr 23.4 LDAP user creaton at first login

Hi,

we plan to raise a Filr 23.4 Standard Deployment for 7000 User. Users should be LDAP-synced from eDir, so LDAP-Server, LDAP-Proxyuser, Containers and everything is configured. This configuration is fine and Users and Groups are created when doing it manually or per Schedule within the Admin-Portal. But i don't want to create 7000 Users in advance, they should be created at first login.

As far as i understand what is documented in  'Planning Filr Users and Groups' : "Register User Profiles Automatically (default): If you deselect this option, then users won't be created until after they log in", this should be possible when deselecting "Register User Profiles Automatically". But Users are not created and can't login as long as they don't exist as a Filr-User.

Is there any configuration that allows 'Provisioning on demand' ? Did not find any hint on this.

Thanks!
Manfred

Parents
  • 0  

    What do you mean "on demand"? What would be your trigger to create?

    I.e. you can run a group in the background. If a user is a member of this group, an account will be created.


    Use "Verified Answers" if your problem/issue has been solved!

  • 0 in reply to   

    A Filr user should be created at first Login of that user if the LDAP filter matches. I don't want to create Filr users that never use Filr.

    I assume, the Option "Register User Profiles Automatically = disabled" is for that purpose.

  • 0 in reply to 

    It should work exactly as you described... on my side it did it befor upgrading to 23.4... Probably an bug... Raise a case at OT and please come back with your results...

Reply Children
  • 0 in reply to 

    Hey guys,

    just a little update:

    I raised a case at OT. It looks like a bug in small deployment. If you reindex, the user creation on first login should work. My case is still open, because i did a reindex couple days ago and experienced the problem again today. So i did a reindex today and now it works. But probably there is still something wrong. 

    I'll keep you updated...