Several categories of people use our application under Natural, the vast majority having an AD account.
However, a minority of people are temporary workers who do not have an AD account and who connect locally to the production site. In this scenario we would like to be able to authenticate with the AD but also verify the account locally.
It would be interesting when the AD is activated in SYSSEC, to check the existence of the account on the AD, but if it does not exist, to check if the account is not known locally in the FSEC. To have a control algorithm close to :
The account exists in the AD :
The password is correct : authorization to enter the application
The password is not correct : connection refusal
The account does not exist in the AD :
The account exists in FSEC :
The password is correct : authorization to enter the application
The password is not correct : connection refusal
The account does not exist in FSEC : connection refusal
Use Case | Team work |