Optional user account

5
What would be the best way to have an optional user account? At the moment I'm using the standard way to give a user account to a certain object: let the object inherit from System.user. But this also means the object must have an account; it's not optional. Now I'm wondering how I can make it so that the account is optional, i.e. if a I fill in a username+password then the object is able to login but if I leave it blank the object simply can't login.
asked
3 answers
6

Hi Dennis,

I think you shouldn't use the 'Derives function'. You can also use a reference to system.user ( or a derived object of system.user), so an account can have a user account, but it is not obliged.

answered
4

Editing the System.Module is not a good idea. See the comment of Benny for Marco's answer.

If the only thing you would like to prevent is users from logging in you could set the attribute System.User.Active to false. The user will not be able to login any more

In case you don't want to fill out a username and password you could use a workaround where you fill the username and password of this user with some random values by MF and set System.User.Active to false and do not assign a userrole. It depends on your application from where you would like to trigger this flow. I can imagine you would create a custom save and cancel button from where you trigger this flow.

answered
-6

What you could do is the following: Go to the derived object: System.User Open this metaobject and delete the validation rules that say that the name and password is required. Once you've done this, you will be able to save an User object without giving it a name and password.

answered