- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2016 11:07 AM
Ok. Logged a call with hi. Reading the wiki only mentions the best way to login on is by providing users with the url with sso sys id as mentioned before.
Sent from my iPhone
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2016 04:22 AM
To mention..we are using Eureka and so does not have the option for 'primary' idp.
Found the below on the wiki which is exactly what I want, but I want to do this prior to upgrade from Eureaka..any thoughts?:
12.1 Fuji
- Provides a property to identify a primary identity provider. The primary IdP is used automatically for all users if they try to access the base URL of the instance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2016 01:04 PM
You could always create an installation exit override to the redirect.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2016 10:17 AM
Russell,
Did you hear back from support? I just upgraded and I have the same issue - users are not being authenticated automatically and if I show them the side_door page and ask them to use the external login link they are asked for their userid and they are logged in. I configured the glide.authenticate.sso.redirect.idp property but this is not redirecting users to the right place automatically.
Cheers!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2016 12:36 AM
Hi,
To be honest..I decided to stick with the SAML 2.0 and ditched the multi for now..as was on Eureka and at this stage only needed one IDP. Planning to go to Helsinki..so once upgraded will add the multi provider plugin back in and set up a primary.
When creating and populating the property: glide.authenticate.sso.redirect.idp did you try prefixing the provider sys_id with "sso:"?..never tried that...i dont think