Problem logging in to Workplace

[mjm23]

Hello Experts, need your help on IX Workplace please.

I am logging in one user to IX Workplace but after putting all the credentials and stuff, it keeps on landing on this UI:

The configs are the same with the rest of the users. Kinda weird coz this is the first time I encountered it.

Thanks!

 

[biglebowski]

probably means the user doesn't have a profile in system manager or is not mapped via AADS.

You can test the user lookup by going to the autoconfig URL and entering the username/password, if it is working correctly you will get a load of config displayed.

 

[mjm23]

Its actually in the SMGR and mapped via the AADS. Its just so weird it is acting like this.

 

[avayaguy23]

Go to the settings>support>Report a problem and then investigate from the logs.

 

[biglebowski]

Also traceSBC to see if TLS and http are behaving correctly

I've had that a few times and it's normally when AADS can't find the user, if you are using an AD sec group for your workplace users have you added him/her to the group?

The quickest test is to get the user to open the autoconfig URL in a browser and try to log in, if they get a config back then the AADS config etc is ok.

 

[mjm23]

I found this in the logs:
## SIP details (SIPUSERNAME, SIPDOMAIN, SIPHA1) that satisfies the requirements (COMM_ADDR_HANDLE_TYPE = null and COMM_ADDR_HANDLE_LENGTH = null) are not found on SMGR.

But i can confirm that the user is in SMGR.

 

[mjm23]

When I login to the autoconfig URL, I get this error.

## File Generation Notes
## Avaya Dynamic Configuration Service does not recognize User-Agent - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.60 Safari/537.36 Edg/100.0.1185.29

## SIP details (SIPUSERNAME, SIPDOMAIN, SIPHA1) that satisfies the requirements (COMM_ADDR_HANDLE_TYPE = null and COMM_ADDR_HANDLE_LENGTH = null) are not found on SMGR.

 

[biglebowski]

That error indicates that they don't have the config setup in SMGR (or it's wrong)

Check that the communication address > Avaya SIP handle is correct, they have a session manager assigned and app sequences etc.

Personally I'd just delete the user from SMGR and re-create from scratch

 

[mjm23]

Yup. Double-checked all the configs and already re-created the user. This one is really a one-off. Does the Active directory or AADS has something to do with this? AADS syncs with the AD everyday BTW.

 

[kyle555]

## SIP details (SIPUSERNAME, SIPDOMAIN, SIPHA1) that satisfies the requirements (COMM_ADDR_HANDLE_TYPE = null and COMM_ADDR_HANDLE_LENGTH = null) are not found on SMGR.
So that means you logged into AADS ok.

What's wrong is that AADS can't correlate you to your SMGR user.

In the attribute mappings, there's one for SMGRLoginName that is "mail" by default.

So that means your AD user must have some attribute that = the SMGR user name.
And that AD user must be in a group that you published AADS settings for that has the automagic SIP thing working.
And SIPSSO must be 0 in that group level config.

So, what extension are you expecting to automagically login?
What is that user's login name in the SMGR Identity tab?
What AD attribute = that SMGR Login Name on that identity tab?
Is that attribute correlated to SMGRLoginName in AADS's LDAP configuration?

If all of the above matches, sometimes running app configure and redoing the Cassandra database sync with SM help.
You do have the SMGR configuration of a "data center" and the AADS being paired off with a SM, right?

 

[mjm23]

Issue was in the AD part. Admin has left out one of the user group case closed