Is there a concrete release date for the “post-identifier trigger” feature?
Welcome to the Auth0 Community!
We don’t have a concrete release date for this feature and will update here when we have more information. Thank you!
@dan.woda,
ok, thank you for the update. Looking forward for the new feature.
1 Like
Hey there!
As this topic is related to Actions and Rules & Hooks are being deprecated soon in favor of Actions, I’m excited to let you know about our next Ask me Anything session in the Forum on Thursday, January 18 with the Rules, Hooks and Actions team on Rules & Hooks and why Actions matter! Submit your questions in the thread above and our esteemed product experts will provide written answers on January 18. Find out more about Rules & Hooks and why Actions matter! Can’t wait to see you there!
1 Like
Hello, where are you in the development of the pre-login feature ?
Welcome to the Auth0 Community!
As mentioned in this thread, there is active development for a post-identifier feature.
hi, curious if there’s any update on this?
we have the same use case as @skylar above, namely, we want to enforce SSO for certain domains, and its a very frustrating experience to have to go into the application and then redirect them back to the login page
it seems like the best way around this right now is to go back to using Auth0 rules, which doesn’t seem ideal
2 Likes
Has this feature been released or is it on a roadmap yet? I see that if you click on the actions Library and click Choose From Template there is a tag that looks like this feature is somewhat released, but not other places in the UI.
1 Like
Use case:
Manipulating the email address for username (such as stripping special characters).
Yea, we can’t do email first because Auth0 has been far too lazy to implement anything since they got acquired. A sad state!
We need a hook that lets us take the user’s email, figure out what organization they belong to and then redirect them to their SSO. But no… three years I’ve waited
I remember Auth0 in 2017-2019 when they actually cared about customers and winning
2 Likes
As many have stated, it would be very helpful to have a pre-login action to handle more complicated federated authentication scenarios. Home Realm Discovery, while nice, is too broad and doesn’t allow per-user or per-app federation, for example.
We are using passwordless login with OTP via email, and we have a requirement to identify whether the user is registered or not during login. However, for unregistered users, Auth0 displays a message stating that an OTP has been sent to the provided email ID, even if the email is unregistered.
In this case, we need to redirect the user to a custom error page instead of showing the message that an OTP has been sent. To achieve this, we need a “pre-login” script that executes every time a user attempts to log in using either passwordless authentication or email and password.
Since the “pre-user registration” script does not trigger when an unregistered email is entered, we are unable to determine whether the user is registered. The issue with the “post-login” script is that it executes only after the user has successfully logged in, which does not help in achieving our required functionality.
I was directed by my account team to enter a feature request for the post-identifier feature. As you note, this appears to be (or was) under active development. What is the most appropriate way to vote for its importance in an upcoming release?