@andre said in FUSIONAUTH_KICKSTART is deprecated, what is the new name?:

FUSIONAUTH_APP_KICKSTART_FILE

Actually FUSIONAUTH_APP_KICKSTART_FILE works.

I am not using elastic search. But I thank you for your help, but I am getting to it a different way. I have stuffed the use's email into the "state" variable and then on the app side I am using that as an index. So while it is not the most "pretty" solution, I think it might work.

Upgrading to v 1.19.7 seemed to work. thx

That is one path that might work in the future, but you can't create arbitrary registrations, call the APIs, or know which groups someone is part of right now.

I know the roadmap includes reworking the lambda so that it is more flexible. That's tied up in upgrading from Nashorn. If we allowed you access to any APIs from the lambda, you'd then be able to do this.

See https://github.com/FusionAuth/fusionauth-issues/issues/571 and https://github.com/FusionAuth/fusionauth-issues/issues/267 for more on that. If you can, it'd be great to comment pointing to this forum post about wanting more flexibility in Lambdas.

You can implement any password hashing scheme as a plugin and load it into FusionAuth. Then you simply migrate the user using new scheme. There is a tutorial on that matter in the docs.

Nope, there's no way to know when passwordless logins have expired via webhook.

You have a couple of options:

You can create a github issue specifying your use case. I'm not sure how quickly this feature would be implemented, however, as this is the first request I've seen. You could note when you send the passwordless login on the user object (in user.data) and build a query that shows all the users with expired passwordless logins. You can know when you sent it and how long it is good for by querying the tenant settings, which gives you the time it expires. You could note when you send the passwordless login in some other external database and process it there.

Added a doc bug: https://github.com/fusionauth/fusionauth-issues/issues/1005

Hiya,

Can you please provide more details:

any logs (esp with debug enabled) what version of FusionAuth are you running? configuration of the SAML provider, including everything outlined here: https://fusionauth.io/docs/v1/tech/identity-providers/samlv2/ what docs you used on the okta side

I know we have customers who have succeeded in using Okta as the Idp and FusionAuth as the SP, so would love to get to the bottom of this.

Hiya,

Do you have a script or set of scripts which illustrates a valid user enumeration attack against FusionAuth?

I did a test of three kinds of user login:

existing user, valid password existing user, invalid password user who didn't exist

And they all returned in roughly the same amount of time.

Works perfectly now. TY!

On reading through your linked document, FusionAuth doesn't support this natively. There's no 'sso' endpoint which does what the docs say must be done (checking the signature, creating the new payload, etc...).

You have a couple of options:

file a feature request: https://github.com/fusionauth/fusionauth-issues/issues explaining what you'd like to have done use OIDC for discourse (which should work with FusionAuth out of the box): https://meta.discourse.org/t/openid-connect-authentication-plugin/103632 set up a small proxy server which would receive the SSO request from discourse, present a login screen, and call the FusionAuth Login API to authenticate the user

I'd probably recommend the OIDC route unless there's some reason why it wouldn't work for you.

Solved. The error code coming back is [duplicate]user.email. I just need to ignore that!

Yup, you got it!

And also HMAC keys will never be displayed in the public-key list. Since they are symmetric, displaying them in that list would let anyone viewing them sign JWTs indistinguishable from those signed by FusionAuth.

Should I be working with the email template or is that for something else?

I'd look at email templates and tweaking those, yes. https://fusionauth.io/docs/v1/tech/email-templates/email-templates/ has some docs about this.

Is a client_id and a user_id (returned from registration) the same thing?

Nope. client_id represents an application in FusionAuth. user_id represents a user.

Hope that helps, glad you're getting close!