Topics created by dtokarz1

@dtokarz1 That's great! Glad you figured it out, and thanks for letting us know.

Thanks @dtokarz1

I agree; this would be a nice feature to implement for edge cases.

Thanks,
Josh

Ah, thanks, that makes sense.

Each application can have a username (in the registration object). That username can't be used to login, but it can be used for display purposes in your application: https://fusionauth.io/docs/v1/tech/apis/registrations/

You could allow people to register/login with email address/password and then let them choose their registration.username for use in the application (you'd have to build a page with a form that would use an API key to let them do so). Now that I think about it, I guess you could do the same with user.username, which is the username they can log in with. So that might be an option.

Anyway, good luck and let us know how things go!

I rolled back and installed an elastisearch container. Added the SEARCH_TYPE in the fusionauth deployment and mapped a service to the same RDS DB and it stood up without an issue. Something screwy in the way Fusionauth is connecting to either Postgre or MySQL.

I'm going to have to talk to sales as I want to enable the features temporarily to use it as a POC. Also so I can justify the cost per month for actual support beyond forums.

Thank you for your time.