Replies: 1 comment 2 replies
-
Hey @anon474 Can you tell me a bit more about your setup here. Are you talking about JIT for computers or JIT for roles? JIT for computers uses AD sites to try to locate the closest DC for that computer, which is where it will make the JIT group modification. So we wouldn't expect to see an issue here, unless there was a problem resolving the client site. JIT for roles currently uses the AMS server's DC to make the change. So there could be a delay if the service you are JITing into is in another site. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What solutions are you guys using to lower or remove the delay time when updating the JIT access group? I currently have to wait 5-10 minutes for AD sync to replicate out to all the DCs before I can use the JIT access. I know that I can do a force AD sync, but I'm looking to find a way that didn't require a manual AD sync after every JIT request.
Beta Was this translation helpful? Give feedback.
All reactions