Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
SSOServlet working on 2nd attempt
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
53
Members:
0
Total:
53
Online Now:
New Topics
Top Forum Posters
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
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Infor / Lawson Platforms
S3 Systems Administration
SSOServlet working on 2nd attempt
Please
login
to post a reply.
1 Replies
0
Subscribed to this topic
29 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
Roger French
Veteran Member
Posts: 549
New Poster
Congrats on posting!
10/31/2013 2:32 PM
Has anyone seen or heard of this condition before?
If I am on the server where LSF is installed, and I attempt the URL:
http://
/sso/SSOServlet
I get the login page. I enter the correct ID and password (LSF is bound to AD).
However the first time I attempt to log in, it does not work, and brings me back to the login page.
The 2nd time, I enter the same login credentials, and voila it works.
Regular Portal login works on 1st attempt.
This is win2008 on LSF 10.0.2
I don't see anything in any of the LSF logs or on the server logs.
If I am remoted into another server, and I try the same exact thing, the SSOServlet works fine and OK with no issue on the very first time.
Kwane McNeal
Veteran Member
Posts: 479
Helpful Replier
Thanks for being such a helpful replier!
MVP
You're an MVP!
10/31/2013 2:56 PM
Split
Roger,
Yes. This is usually an issue with LDAPBind using a domain name / multihomed A-record (aka DNS 'group') as it's target authentication source, as opposed to a single server. Your issue is that one of the hosts is either not an AD forest controller, not enabled with the FSMO role of Global Catalog on at least one of the hosts.
Kwane
Please
login
to post a reply.