We'd love to hear about it! Click here to go to the product suggestion community
I have a single user that cannot login to the End User Portal.
Things I have checked looking at other forum threads:
I did notice that the user in question did not populate under the users tab, however my brand new test user did.
Here are the log entries:
"I did notice that the user in question did not populate under the users tab, however my brand new test user did."
Hmmm. Try an experiment. At the bottom of the 'Advanced' tab in 'Definitions & Users >> Authentication Services', configure 'Prefetch Directory Users' to sync your problem user and hit [Apply]. Start the Prefetch Live Log, wait for a moment to give it time to start up and then click on [Prefetch Now].
My guess is that the remotely-authenticated user object won't be created because there's a conflict with an email address entered for a locally-authenticated user object. What did you see?
Cheers - Bob
In reply to BAlfson:
No errors in the log, however the user was created successfully and can login to the User Portal now.
No idea what the issue was.
I have another user that is experiencing the same thing. I would much rather fix the underlying issue rather than prefetch as a workaround. Any thoughts on things that I can try?
Or should I just prefetch as a standard? I have less than 50 users at this location.
In reply to SCCIT:
If prefetch won't work, it's because there's already a User object that conflicts with the remotely authenticated one you're trying to create. This would be a user with an identical name or email address.
Prefetch does work. I do not manually create any user objects, they are all created by the UTM so I'm not sure how there would be a duplicate?
If I had two users in AD, Bob1 and Bob2, and they both had email address email@example.com, Bob2 could not be synced if Bob1 already existed in the UTM as a remotely-authenticated user object. You should see any conflict in the Prefetch Live Log.