Rich client login error

 9 Replies
 1 Subscribed to this topic
 32 Subscribed to this forum
Sort:
Author
Messages
BDT
New Member Send Private Message
Posts: 5
New Member
Hi ,

I have successfully installed Landmark product but when i try to log in to the rich client interface with Lawson log in credentials it gives me invalid user name/password error. Is there a default log in credentials for Landmark or can I create a new user ID to log in. Please help me solve this issue.

Please refer the attachment for more information.

thanks
regards
BDT

Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
A basic install creates only the OS identity for actor 'lawson'. You'll need to create the rest manually.

Kwane
BDT
New Member Send Private Message
Posts: 5
New Member
Hi ,

Can you please explain how to create a new identity manually.

Thanks
regards
BDT
elessarfl
Basic Member Send Private Message
Posts: 4
Basic Member
Hi BDT and Kwane,
We are getting the exact same error msg. What is the resolution to this issue?
Thanks
PKS
Advanced Member Send Private Message
Posts: 23
Advanced Member

Hi All ,

My customer is also facing the same issue for users .

 We are on cloud and ADFS is complete

1) User has thick client identity 

2) Required roles are available 

I am able to login as lawson (cloud domain) 

Apart from the above what else do I need to check 

Carl.Seay
Veteran Member Send Private Message
Posts: 109
Veteran Member
On cloud, make sure you're using the domain when logging in (user@domain.com). Also, make sure 'ignore case' is checked off on the SSOP login scheme.
PKS
Advanced Member Send Private Message
Posts: 23
Advanced Member

Hi Carl , Thanks for the response .

Where should I be checking this ?

Carl.Seay
Veteran Member Send Private Message
Posts: 109
Veteran Member
In Rich Client, under the GEN product line. There is a menu option for Login Schemes. It would be a custom name, but it probably has LDAP_BIND or ADFS in the name.
PKS
Advanced Member Send Private Message
Posts: 23
Advanced Member

Thanks Carl .

 

 

PKS
Advanced Member Send Private Message
Posts: 23
Advanced Member

Just came back to update on my problem cause and solution

 

This customer's LDAP tree was not following standard format

 

Userid1@company.XXX ,userid2@company.YYY

 

I had to match the thickclient identity to match as per IFS