I have the logins working for both Users and Agents using the same OAuth configuration connected to OneLogin. I am not sure where the issue lies (OneLogin/IdP/Oauth or osTicket configuration).
Here is the scenario:
I as an agent go to the /scp page, and log in clicking the SSO button. Works. My name displayed is "John". Great, would prefer the whole name but that's possibly a separate issue or configuration..
I as a user (same account as agent) go to log into the Client side (without existing as a customer/end-user), click on the SSO button and it authenticates me. However, my name is displayed as "Jdoe" (first name first initial+lastname). So the system creates my account (expected), but the naming isn't the same.
I've tried to set up an oauth for Client and a separate one for Agent and same situation. Actually it's worse because there seems to be an issue with "duplicate values in the database" errors that happen and my agent can't log into client, or vis versa..
So my question is this in regards to Oauth:
I'd like my end-users to log into the client page using the oauth, and for the system to display their name (preferably their full name [John Doe], but first name is fine [John]). I would like their username that is created when they log in/authenticate to be the same as the oauth/SSO system (jdoe).
I'd like my agents to log into the SCP page using the oauth, and for the system to display their name (preferably their full name [John Doe], but first name is fine [John]). I would like their username to match that which was created in the Agent side (jdoe). I'd additionally like to have my agents be able to sign into the client side and display the same exact stuff.
I'm not sure it's possible, but am open to discussion about it
