@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?

@benlabbe2007 What version of FusionAuth are you running?

@atabakov Can you please share the settings for the application in that Admin UI? Please do not include any secrets.

@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.

@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.

@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.

@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.

@michaelgaffney278 Is there a reason you would like to keep the existing users on the old hash? It doesn't seem like it. If you would like to rehash all users when they login, please check this out. It talks about rehashing all passwords for a custom hash, but if you select an existing hashing scheme, it should convert it as well. Is this what you are after?

I would think you could migrate all the existing users with your custom hashing, then at some point switch the hash setting and be where you want.

I would test this out before trying in production, but it may do the trick.