• Replies 11 replies
  • Subscribers 0 subscribers
  • Views 71 views
  • Users 0 members are here
Options
3sides - Social sharing widget
Related

HighQ and SSO

Athar Agha
27289

Not sure if this is possible but curious as to current capabilities..

I understand that HighQ can accept identity providers 'upstream', in that placing an IDP 'before' HighQ will allow authentication into HighQ ("You've logged into Okta, so you can now access HighQ").  Is there any capabilities that will allow HighQ to act as an IDP?   ("You've logged in to HighQ so you can now access site x") ? 

i.e. we want to be able to validate a user login request at HighQ and pass that SAML response downstream instead of it stopping at HighQ so we can authenticate other systems..

I know this wasn't possible last year as it looked like there was no way to pass that response downstream, but wondering if things have changed now that TR are at the helm?

Thanks

Parents

  • Peter Simpson thanks!

    I wasn't sure what a specific implementation would be like.

    The "Login with MSFT or Google" (NOT Facebook!) was one idea to simplify things for our clients.

    Another idea was if we had a central login mechanism. For ex, a client comes to our web site and there is a "Login to access all Jackson Lewis Services" button. Clients login there -- perhaps we would include the "Login with MSFT" button -- and then would be shown a list of services available to them -- like Collaborate, Home Grown Services and any other third-party services we license and make available to clients -- and then could log straight in to those b/c they have already been authenticated to our central login mechanism. I guess in a sense -- and I am not being very knowledgeable about this -- our firm's central login hub would serve as the IDP?

    The approach you mention above might be workable for a small number of large clients, but the fact that we would need to set this up per client would not allow it to scale and likely does not give us the type of centralization we are looking for.

Reply

  • Peter Simpson thanks!

    I wasn't sure what a specific implementation would be like.

    The "Login with MSFT or Google" (NOT Facebook!) was one idea to simplify things for our clients.

    Another idea was if we had a central login mechanism. For ex, a client comes to our web site and there is a "Login to access all Jackson Lewis Services" button. Clients login there -- perhaps we would include the "Login with MSFT" button -- and then would be shown a list of services available to them -- like Collaborate, Home Grown Services and any other third-party services we license and make available to clients -- and then could log straight in to those b/c they have already been authenticated to our central login mechanism. I guess in a sense -- and I am not being very knowledgeable about this -- our firm's central login hub would serve as the IDP?

    The approach you mention above might be workable for a small number of large clients, but the fact that we would need to set this up per client would not allow it to scale and likely does not give us the type of centralization we are looking for.

Children
No Data