How to delete a user from an imported Document Vault

Hi Emmi,

Thanks for your feedback. I agree with you. It seems to me that they have
split up the Access Security in 2 layers.

The first security layer deals with user authentication for the server: Who are you? Do we know you? These credentials are specified in the Login Account,
so with a Login Account you can get on to the M-Files Server.

The second security layer deals with Authorization. Which vault can you access?
What permissions do you have for a particular vault? All the authorizations/ permissions a user has, are specified in the User Account.

Therefore, it makes sense that you first need to have a Login Account, because if the server doesn't know you, it will not be able to decide whether or not you are allowed to create a User Account.

You wrote:
"I think the user account should be at least disabled if the login account is removed?"

When the Login Account has been removed, it doesn't matter whether the
User Account has been disabled or not, because the User won't be able to get on to the Server anyway.

You wrote:
"Is there a possibility or some needs for the situation where the is a User Account but not Login Account? "

The only situation I can think of is when the M-Files application is being migrated, for example from a PC to a rack-mounted server. In that scenario
you don't want to lose the User Accounts, but there's a good chance that
the Authentication and Authorization mechanism will change, which would require setting up the Login Accounts from scratch. In this case there is no need to change the User Accounts just because M-Files will run on different hardware.

I've also found that writing stuff down creates a better understanding of the subject.

Thanks & regards,

Carl.

Hi Emmi,

Thanks for your feedback. I agree with you. It seems to me that they have
split up the Access Security in 2 layers.

The first security layer deals with user authentication for the server: Who are you? Do we know you? These credentials are specified in the Login Account,
so with a Login Account you can get on to the M-Files Server.

The second security layer deals with Authorization. Which vault can you access?
What permissions do you have for a particular vault? All the authorizations/ permissions a user has, are specified in the User Account.

Therefore, it makes sense that you first need to have a Login Account, because if the server doesn't know you, it will not be able to decide whether or not you are allowed to create a User Account.

You wrote:
"I think the user account should be at least disabled if the login account is removed?"

When the Login Account has been removed, it doesn't matter whether the
User Account has been disabled or not, because the User won't be able to get on to the Server anyway.

You wrote:
"Is there a possibility or some needs for the situation where the is a User Account but not Login Account? "

The only situation I can think of is when the M-Files application is being migrated, for example from a PC to a rack-mounted server. In that scenario
you don't want to lose the User Accounts, but there's a good chance that
the Authentication and Authorization mechanism will change, which would require setting up the Login Accounts from scratch. In this case there is no need to change the User Accounts just because M-Files will run on different hardware.

I've also found that writing stuff down creates a better understanding of the subject.

Thanks & regards,

Carl.