FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login
    1. Home
    2. stunny
    3. Topics
    S
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 5
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by stunny

    • S

      Email verification link not updating from template

      General Discussion
      • • • stunny
      3
      0
      Votes
      3
      Posts
      592
      Views

      D

      I'm also facing the same issue. When someone send me email. I am totally unable to get it in my inbox or spam folder. What is the appropriate solution to come out from it.

    • S

      Creating a FA browser session after server-sided sign-up

      General Discussion
      • • • stunny
      4
      0
      Votes
      4
      Posts
      455
      Views

      S

      @dan But is it possible to initiate the FA session?

      Custom form is used for registration, it's on a separate page than the actual application (X). Let's say after the registration I get the token from FA on the server side. I can send it back to the client side and save it there. This way, when the user visits login page, I'm able to send the token to the server and from there to FA for checking.

      But what if there's a second separate application (Y). In this app user tries to login, gets redirected to the FA login page. However, he's not recognized by FA here and is asked to enter his password.

      I've read and tested your SSO example app, but it doesn't answer my case. Is it possible to do so that FA recognizes user when he is redirected from application Y after registration in application X's custom form? Thanks

    • S

      Cross-platform SSO

      Q&A
      • • • stunny
      4
      0
      Votes
      4
      Posts
      659
      Views

      M

      What do you mean by 'user logs into desktop application'? How would you like to implement it?
      If you implement step 1. as I've described in my previous post (by opening the browser window to log the user in) then there will be an SSO session in the browser already.
      This is the flow that OAuth specs define for native applications, eg. desktop ones: https://datatracker.ietf.org/doc/html/rfc6749#section-9

      This means that in step 3. when the browser is opened, the user is already authenticated.