• Home
  • Categories
  • Recent
  • Popular
  • Pricing
  • Contact us
  • Docs
  • Login
FusionAuth
  • Home
  • Categories
  • Recent
  • Popular
  • Pricing
  • Contact us
  • Docs
  • Login

Fusion auth single sign on issue

Scheduled Pinned Locked Moved Unsolved
Q&A
2
2
2.2k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M
    mr.sahand
    last edited by 25 May 2024, 13:59

    I have two same enabled applications defined on fusionauth each representing a separate web application hosted on my local. I have also created two applications on an azure ad tenant and connect my fusion auth applications to them via two saml v2 identity provider I have created on fusionauth. I have created one user on AzureAD tenant and only added that user to one of the applications.
    I can launch the web application which the azure ad user has access to and log into the application using it. Now when I try the other web application on the same browser what happens is it logs into the application without even going to a login page. What I am expecting is the second application to be rejected to log in as the azure ad user does not have access to it.
    What do I need to acheive the desired behaviour?

    S 1 Reply Last reply 24 Jul 2024, 10:05 Reply Quote 0
    • S
      staffordjeffrey996 @mr.sahand
      last edited by 24 Jul 2024, 10:05

      @mr-sahand said in Fusion auth single sign on issue:

      I have two same enabled applications defined on fusionauth each representing a separate web application hosted on my local. I have also created two applications on an azure ad tenant and connect my fusion auth applications to them via two saml v2 identity provider I have created on fusionauth. I have created one user on AzureAD tenant and only added that user to one of the applications.
      I can launch the web application which the azure ad user has access to and log into the application using it. Now when I try the other web application on the same browser what happens is it logs into the application without even going to a login page. What I am expecting is the second application to be rejected to log in as the azure ad user does not have access to it.
      What do I need to acheive the desired behaviour?

      I am having the same single sign on issue now. Did you find any solution?

      1 Reply Last reply Reply Quote 0
      • First post
        Last post