Product Ideas
Share your suggestions and ideas. Vote on ideas you find valuable.
Share your suggestions and ideas. Vote on ideas you find valuable.
Do you want to play a crucial role in shaping Jet Global products?
People feel very bad about steadily type in their Login data to get to their Reports in the Jet Web Portal. Moreover many users even don't know about what "Domain" means as they are no heavy user.
Guest
Jet 2019 R2 (20.0.19116.1) - released April 30 2019
Single sign-on to Jet Hub can now be accomplished using O365 authentication. There is an option at install to specify this, and a Client App setup in Azure Active Directory is required to support it. Azure Active Directory integration is also an option to accomplish this. Be advised that you cannot migrate from AD to AAD at this time.
Review the following Help Center article for more information: https://support.jetglobal.com/hc/en-us/articles/360020106914-Installing-the-Jet-Service-Tier-Jet-Hub-with-Active-Directory-and-Single-Sign-On
Hello Cristian,
Yes, we are planning on providing SSO with Windows AD using O365 authentication. This will require you to register a client application in Azure AD.
More details will be coming out soon once the beta starts.
Hi Kim, Will the SSO work with Windows AD as well, or only Azure AD?
If only Azure AD, how so?
Kind regards, Cristian
Jet has been working on developing Single-Sign On access using O365/Azure AD.
We are looking for some Jet customers who are familiar with Azure Active Directory and Jet installation to run through our installation instructions using a test environment that we provide. This is an activity run by the Jet UX Research team. It will take approx 45-60 minutes. If you are interested, please sign up using the following link: AAD Study Intake(study has ended)You may also contact me directly at kimd@jetglobal.com with any questions.
The domain is only part of the problem The main Point is that we get Feedback from the customers that they don't want to Login several times a day and entering their Passwords. As they want the link to a Dashboard to be started inside of NAV they always have another logon.
Unfortunately even the username is sometimes a problem, because some users have NAV-Usernames (not AD-Usernames) and when they open JET Web Portal out of/next to NAV they don't get it that they have to enter the AD-Login whereas they Login to NAV with another username. This sounds strange, but it's a fact. So they call the Hotline that they can't Login to the Jet Web Portal. Think at least about Azure AD-Integration!
@MichaelZettl, we are planning to change the Jet Web Portal logon experience to auto-detect the domain and populate the domain field. The domain can be overridden by using username@domain or domain\username conventions. Would this satisfy your needs?