12-24-2014 12:55 AM - edited 03-10-2019 10:18 PM
Hello Team,
Ive created a guest account in the sponsor portal for a test guest user, however the state remains in "created" state.
Now when the user tries to log on via the sponsored guest portal the error back is "invalid username or password".
In ISE logs it says :
Overview
|
Authentication Details
|
Any ideas why this might be, if im doing something wrong and how to fix?
Thank you
Bilal
Solved! Go to Solution.
04-14-2015 02:21 AM
I have had the same issue, the fault is caused by the time zone in the sponsor groups being set by default to UTC, so if you are in London the accounts wont become available until UTC time. The best practice is to add a local time zone and remove UTC at initial configuration
To resolve this create a new local time zone in Guest Access>Settings>Guest Locations and SSIDs then under Guest Access>Configure>Sponsor Groups amend the time zone properties in each sponsor group
One other problem is if you do not remove this at initial configuration you don't seem to be able to get rid of UTC, not really an issue unless you forget when creating new sponsor groups
12-29-2014 01:52 AM
Conditions:
Guest uses a timeProfile fromFirstLogin and didn't logged in before timeProfile validity time
Workaround:
Reset Guest account validity from Sponsor portal fixes the issue temporarily (the same situation will occur if guest do not login).
04-14-2015 02:21 AM
I have had the same issue, the fault is caused by the time zone in the sponsor groups being set by default to UTC, so if you are in London the accounts wont become available until UTC time. The best practice is to add a local time zone and remove UTC at initial configuration
To resolve this create a new local time zone in Guest Access>Settings>Guest Locations and SSIDs then under Guest Access>Configure>Sponsor Groups amend the time zone properties in each sponsor group
One other problem is if you do not remove this at initial configuration you don't seem to be able to get rid of UTC, not really an issue unless you forget when creating new sponsor groups
04-14-2015 03:30 AM
I confirm, it's the solution.
Well done.
02-17-2016 01:25 AM
The issue is caused by incorrect time zone all goes back to when the ISE was first installed and you select the wrong time zone there, eg if in UK you select UTC instead of GB (best to select GB).
When you create your guest portal and use UTC time zone as your local time there is an hours difference so when you create the user account it sees it as not active yet, if you wait an hour you would then be able to log in. I usually use London and remove the default time zone from the portal.
02-16-2016 09:29 AM
Hello,
I am having the same problem but the difference is that I have ISE 2.0. I already did the recommendations and still get the same situation.
My ISE is using NTP as the time source and shows the correct timezone. I edited the Guest Locations and SSIDs parameters to match the correct timezone.
The guest tries to self-register, gets the username and password but when he tries to log in the authentication fails and I receive the log message saying that the account is not yet active.
I don't know what else to try.
Any ideas?
02-16-2016 09:59 AM
I was able to resolve my problem. I had to go to Guest Locations and SSIDs and leave the default setting for San Jose. Instead of using my local timezone I used UTC. Don't know why this solved the problem but it did.
01-12-2015 06:49 AM
Have you checked the identity source sequence
02-10-2015 09:51 AM
Hello,
Have you found a solution about your issue ??
thx
regards.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide