I don’t know if anyone’s noticed this yet, but if you use concurrent licensing in R4, along with Active Directory login methods, the system produces incorrect error text.
When our session limit is reached, each subsequent login gets an error message of
When in fact it should show some sort of “License Limit Reached” like it did back when we used enterprise licensing.
Does anyone know of any way to correct this?
I could of course find the actual error text and replace it entirely, but doing so would mean that should we have an actual authentication issue (such as when users try to access BOBJ who really aren’t in our AD group) they would get the wrong message.
My current plan is to edit the message text if I can find it, with a sort of either or message (ie: “If you’re seeing this error message it means EITHER: A or B” ).
Ultimately I’d like to fix the problem, and I suspect that there’s just some code somewhere that is incorrect in a webpage.
Yes I’ve opened a ticket, and the tech actually agree’d that something does look odd in BI4. We did not discuss changing the error text just yet as we believe we’ve found a bug.
We tested things several ways and found:
Enterprise Logins - Shows the correct error message when Concurrent Licensing is full
Active Directory Logins (No Single Signon) - Shows the correct error message when Concurrent Licensing is full
Active Directory Logins (Using Single Signon) - Shows the WRONG error message when licensing is full. It shows an Authentication Error message instead.
It’s behaving as if there is a bug in the Single signon code. We think that the system is taking the user credentials and trying to authenticate it with AD… however when BOBJ goes to try it first checks it’s licensing and thinks “Ohhh I have no licenses , therefore I cannot check AD” and it then returns a non-successful AD check (aka credential check fails).
Right now I’m waiting on them to duplicate it in thier test systems and then figure out which engineering team handles that area.