To ensure that our customers really purchase a license per user, we want to set 'max # session per account' to 1 in IAM.
However, this leads to problems in our application, because we also have functionality executed for certain functions via a url call under the user name of the applicationpooluser.
And we notice that it is necessary in our EVO application that the user name of the application pool user needs multiple sessions simultaneously.
So here's the question of how we can achieve this...
Our proposal is, for example, to make it possible to indicate at user level that it may have multiple sessions simultaneously within an application, while for that application it is set that 'max # session per account' is set to 1
Hi Eric,
I assume with ‘application pool user’ you are referring to a service account used for programmatic API access? Claims are always done for the acual user, not the web application pool user or the database pool user. (It could be that this user is used as service account in your case).
That being said - We can add an option for users in IAM that they are not limited by the applications’ Max. # sessions per account settings. This could then be enabled for specific service accounts. Would that suffice?
Hello Anne,
The webapplication user is in our case also defined in the IAM as a normal user.
Your suggestion 'We can add an option for users in IAM that they are not limited by the applications’ Max. # sessions per account settings. This could then be enabled for specific service accounts.' would be a nice solution for this problem.
Bye Eric