Yep.
1 Like
Everything in the config file looks correct. Only the company that had the domain migration is down, the other companies are fine (and we all use the same config file).
I swear @josecgomez just went over AD auth tokens in azure on a different post related to someone coding an API call or something… does it relate to this too maybe. I will try and find the post.
Do you have to create something new here?
Delete everything here @aosemwengie1
%AppData%\epicor\AzureAD
On the client. I suspect if you had an old token in there it is trying to use the token with the wrong key.
6 Likes
I went back and read, you said domain migration…
Did you create a new Azure AD App after the migration and update the Azure Settings within Epicor as well as in the SysConfig File?
I’m not sure what “Domain Migration” means but it smells as something that would require a new Azure App be created and re-configired.
2 Likes
If the azure app needed to be recreated why would the browser login still work?
1 Like
That’s a good point, did you try deleteting that file?
5 Likes
Trying it now
1 Like
Omg it worked. Thank you!!!
9 Likes
Has Epicor always used this folder even in 10?
Yes as far back as when they introduced Azure Login whenever that was.
2 Likes
My guess would be that the browser does not look at that file… it’s for a Smart Client configuration. Browser-based doesn’t require anything at all on the local file system, just the browser itself.
Just a guess.
1 Like
That was the point I was making lol. That the problem HAD to be a local file, because otherwise the browser login would also be broken. I just phrased it as a question.
4 Likes
Thanks