Forum Discussion
NimbostratusF5 APM and Exchange 2013 with multiple domains for authentification
Hi, I have an Exchange 2013 in a ressource forest with 3 differents domains for authentificate my users (linked mailbox). I have used the exchange 2010- 2013 template to create the APM for OWA. But by default i only can be authentificate in one domain. I have changed the Access policy to get the domain of the user and apply a different aaa server but it's not working. Here is a screenshot of my Access policy:
I'm always sent to the fallback branch on the box: "domain Check". On the other branch rule, I have this expression: expr { [mcget{session.logon.last.domain}] == "myDomain"}
I don't know if the problem is in the expression or elsewhere. Thank you for your help !
5 Replies
Michael_Koyfma1Cirrus
How are you populating the domain variable? Are you setting it in the Logon Page? Assuming you are, try to replace == with contains and see if it starts matching this way.
Nicolas_M_67142I set the logon page to split the domain from the full username. I replaced the == with contains but it's still not working. I also tried to add a new field "domain" in my logon page but it's not working either
- Nicolas_M_67142
here is a trace of my last test:
- Kevin_Stewart
Employee
Just curious, but do you have a branch condition like this?
expr { [mcget {session.logon.last.domain}] equals "ad.groupe.net" }I'd also throw in a test message box directly after the logon page to see what your domain variable is before it gets to the domain check agent. Use this syntax in the message box field:
%{session.logon.last.domain} - Nicolas_M_67142
Hello Kevin, Thank you for your help, it works with your branch condition ! I must have made a mistake in my syntax.
Thanks again !
