Rich client login error - LawsonGuru.com

Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chesca	1042

BDT

New Member

Posts: 5

6/25/2013 4:41 AM

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

Posts: 479

6/25/2013 5:07 AM

A basic install creates only the OS identity for actor 'lawson'. You'll need to create the rest manually.

Kwane

BDT

New Member

Posts: 5

6/25/2013 5:18 AM

Hi ,

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

Thanks
regards
BDT

elessarfl

Basic Member

Posts: 4

8/30/2013 4:53 PM

Hi BDT and Kwane,
We are getting the exact same error msg. What is the resolution to this issue?
Thanks

PKS

Advanced Member

Posts: 23

New Poster

11/25/2015 7:12 PM

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

Posts: 110

New Poster

Engaged Reader

Avid Reader

11/25/2015 10:47 PM

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

Posts: 23

New Poster

12/2/2015 12:54 AM

Hi Carl , Thanks for the response .

Where should I be checking this ?

Carl.Seay

Veteran Member

Posts: 110

New Poster

Engaged Reader

Avid Reader

12/14/2015 4:45 PM

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

Posts: 23

New Poster

12/15/2015 6:39 PM

Thanks Carl .

PKS

Advanced Member

Posts: 23

New Poster

12/16/2015 10:09 PM

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