@gokul-mahajan20

Can you add ----BEGIN to the JWKS certs?

You will need to obtain the default tenantId from the UI.

If you are using kickstart, you have the option to set the default tenantId so that it is predictable.

Will this one work for you?

https://fusionauth.io/docs/v1/tech/client-libraries/netcore/
https://github.com/FusionAuth/fusionauth-netcore-client
https://www.nuget.org/packages/FusionAuth.Client/

We have an open issue for this: https://github.com/FusionAuth/fusionauth-issues/issues/603 Please do vote it up.

We also are investigating OpenAPI which would let you build a C++ library. More here: https://github.com/FusionAuth/fusionauth-issues/issues/614

Finally, I will point out that you can use the REST API and a JSON library and FusionAuth will work just swimmingly. I'm not C++ savvy, but https://github.com/nlohmann/json and https://github.com/jgaa/restc-cpp look like they could be combined to do the trick.

hiya, have you tried redirect_uri? That should work, but it will require you to configure the allowed redirect_uris in your FusionAuth application's OAuth config (on the OAuth tab in the admin ui). wildcards aren't recommended for the redirect_uri due to security concerns (see https://tools.ietf.org/id/draft-ietf-oauth-security-topics-05.html#rec_redirect ).

The other alternative is to pass a state parameter, which should be returned unchanged to you by FusionAuth. You could then have your code look at that parameter and redirect as needed.

You could also look at caching the value in localStorage and retrieving it after login has occurred.

There is no supported client library for Delphi.

I'm also not aware of any community supported client library for Delphi.

But here is a post indicating that someone built at least pieces of an integration layer. I'd suggest reaching out to John Kouraklis and seeing if they have any code to share.

The client libraries all consume the same REST API, so you can use that as a reference: https://fusionauth.io/docs/v1/tech/apis/

404 is a valid response code when using the client library to look for a user by email.

If the user exists you’ll get 200 and if the user does not exist you’ll get 404.

If you are using the client in the browser and don’t want to expose the 404 to the console, adding a try/catch would be a good idea. The 404 is the expected response code when the user does not exist:
https://fusionauth.io/docs/v1/tech/apis/users#response-2

Users using an sdk created by swagger can use OAuth.

FusionAuth supports all of the grants listed there except "Client Credentials" (if that's an important grant to you, please vote on this GitHub issue).

That said, you can log a user in using this API: https://fusionauth.io/docs/v1/tech/apis/login#authenticate-a-user

As mentioned in that document, you can require a FusionAuth API key (information about creating this here: https://fusionauth.io/docs/v1/tech/apis/authentication#manage-api-keys ) which would not be a per user API key. Or you could disable authentication for the /apilogin endpoint:

Authentication may be disabled per Application, see application.loginConfiguration.requireAuthentication in the Application API or navigate to Applications Edit Security in the user interface.
and have users authenticate against that endpoint.

If on the other hand you are asking about application type API keys that are managed by FusionAuth, the short answer is that is not a feature of FusionAuth. Please see this forum post for other options.

@robotdan Ah, I missed that. I was looking at the response section, which had the registration. Thanks!