@rabah-laouadi What information is in the device.description that is not in the info section?

"info": {
    "deviceName": "macOS Chrome",
    "deviceType": "BROWSER",
    "ipAddress": "192.168.65.1",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36"
  },

Or are you specifically trying to get a custom value in your url? If you let us know a little more about what exactly you want to accomplish, we may be able to find a way to get it done.

Also have you seen this post?

@jefferson-piscos, the debug enabled is under the OAuth tab. Go ahead and enable that and check the logs.

Also it is a little weird that you are redirected to a consent screen. Do you have any consents configured? You can go to Settings -> Consents in the Admin UI.

Then you can check the user and see if you have any set for the user you are testing.

Hopefully that will clear it up and you will be good to go. If not, let's see what those logs say.

@jefferson-piscos There are a few things that may be going on. Where are you you expecting to redirect to after successful login? Can you tell if that page is being hit or is it redirecting back to the login page because that is the page you set it to? Anything you can safely share about the application configuration in FusionAuth or code for your redirect page could be helpful.

It terms of tips for debugging, you can turn on "Debug Enabled" for the identity provider and then check the Event Log after you try to log in. Let us know if that yields any useful information.

@michaelginn529 What do you have your "Logout behavior" set to for the application? Any other specific configuration you can share would help as well.

@haziqt Sounds like FusionAuth is up and working except reporting the wrong IP address of the user on login. You may want to consider opening a issue.

@raymondcamden Ha, gald you got it working. Generally, the quickstarts come with a docker file that you can just run docker compose against and it will get you the instance. That instance would be configured to work with the sample code for that quickstart. The application and uses would be created and things like that. If you have it working the way you want, awesome. If you run into other issues, please just let us know.

@raymondcamden Are you using the Quickstart app? If so, you need to use the Docker instance specified in the app. If you just spin up a brand new instance of FusionAuth, the sample app does not exists and that is likely why you are getting the error message. Try using the Docker instance in the Quickstart and you should be fine. Let me know how it goes.

@d-chinguun-0301 It doesn't look like you can pass dynamic custom parameters to a connector. It does seem you can configure custom HTTP headers though. If you only have a few applications for the user to log into, you could potentially set up different connectors, each with their own custom http headers.

Also, depending on what you are trying to accomplish, it may be possible to create a webhook that would respond to an event that could potentially tell an application where their most recent login came from.

@ehallpassofficial From what I can tell, you are right on with using the proxy as the way to go. I don't have specific experience with that so would love to hear from the community on theirs as well. I did find an open issue with this request and suggest you upvote it to give it some visibility.

@edschlough If you take a look at the example code from the webhook documentation, it shows how to return errors. Is this what you are after?