@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.
-
RE: Issue with Getting Started guide, invalid client
-
RE: Generic Connector, OAuth2.0
@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.
-
RE: How to implement mutual TLS (mTLS) with FusionAuth — best practices and real-world solutions?
@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.
-
RE: Is there away to provide error message data from a webhook via either Webhook or Event logs?
@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?
-
RE: Changes not being applied
@benlabbe2007 What version of FusionAuth are you running?
-
RE: OAuth Complete Registration functionality breaks the authorization flow after upgrading to version 1.59.1
@atabakov Can you please share the settings for the application in that Admin UI? Please do not include any secrets.
-
RE: Duplicating an application held in 'Tenant1' to 'Tenant2' stays in 'Tenant1'
@francis-ducharme-0 You may have to parse the json returned from the get and modify a few things. Does the application get created but not work or does the application not get created? I would think you would need to take the relevant parts from the returned application then create the application under a new tenant? Remember you will have to use the new TenantId in the Request Header. If you are not supplying the TenantId, it will use the default.
On a side note: If you are still interested in a duplicate application across tenant feature in the API, you might want to put a request in.
-
RE: Doubling of login records
@sergey_smirnov, it is awesome that you are able to follow and create steps to replicate the issue. To be 100% I'm not sure if this is a bug or a feature request. If FusionAuth is not behaving as you would like it, I would suggest opening an issue on Github. Be sure to include the details and repeatable steps.
-
RE: Duplicating an application held in 'Tenant1' to 'Tenant2' stays in 'Tenant1'
@francis-ducharme-0 Hey, after taking a look, it seems the only way to do it is to get the application you want to use, parse the JSON for the things you want to keep and then format new json for the create. So you can do it, it is just going to take a little extra work. Sorry for the inconvenience.
I'm not sure exactly what you are trying to accomplish, but have you checked out Universal Applications? A bit more documentation on them is available here.
-
RE: Duplicating an application held in 'Tenant1' to 'Tenant2' stays in 'Tenant1'
@francis-ducharme-0 I was unable to tinker with this last week, but didn't want you to think I forgot about it. It is still on my list when I have some availability. Will post if/when I find something.