Replace Auth0 Rules with Auth0 Actions#1375
Conversation
Summary
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
avanscoy
added
the
main-docs
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
hazel-nut
left a comment
hazel-nut
left a comment
There was a problem hiding this comment.
some thoughts since we're in here anyway, though i know the content is largely transposed from the original without editing. we can modify them in a follow-up if you prefer 😊
| const ipaddr = require('ipaddr.js'); | ||
|
|
||
| exports.onExecutePostLogin = async (event, api) => { | ||
| const corp_network = "192.168.1.134/26"; |
There was a problem hiding this comment.
can we use one of the RFC reserved IP addresses for documentation here? https://datatracker.ietf.org/doc/html/rfc5737
There was a problem hiding this comment.
Maybe move the corp_network definition outside of execute function or use a secret for the IP.
|
|
||
| You could also trigger this Action based on other criteria, such as whether the current IP matches the user's IP allowlist or whether geolocating the user reveals they are in a different country from the one listed in their user profile. | ||
|
|
||
| </Callout> |
There was a problem hiding this comment.
maybe we can remove this callout and add this info in normal text after the initial code sample (maybe with some links to content that would help the reader know how to implement some of them, if we have any)? it seems nicer as a transition in a next steps kind of way. :)
|
|
||
| With [Actions](/docs/customize/actions/actions-overview), you can handle more complicated cases than is possible with [passwordless connections](/docs/authenticate/passwordless) alone. For instance, you can add extra precautions to further ensure possession of an email address or device. | ||
|
|
||
| ## Require Multi-factor Authentication for users who are outside the corporate network |
There was a problem hiding this comment.
| ## Require Multi-factor Authentication for users who are outside the corporate network | |
| ## Require multi-factor authentication for users who are outside the corporate network |
There was a problem hiding this comment.
I think this example use case could be moved to a centralized catalog of example using Actions and reference it from here. And also have two other link referencing how to set up a Custom Phone Provider and Custom Email Provider Actions which have direct relationship between Extensibility and Passwordless.
There was a problem hiding this comment.
The catalog discussion is the right direction, though part of a much broader docs expansion that we are currently in the early stages of figuring out. As for the two examples, should we replace the post-login with custom-phone-provider and custom-email-provider examples? cc @avanscoy
There was a problem hiding this comment.
Let's do two iterations, this one replacing the custom-phone-provider and custom-email-provider. It's a good call out!
The other iteration will talk longer.
Co-authored-by: Hazel Virdó <hazel.virdo@okta.com>
sample-use-cases-rules.mdx was deleted in this branch (replaced by Actions version) and modified on main (meta description update). Keeping the deletion as intended by this PR. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
4 participants
Description
Replaces an article on Auth0 Rules with Auth0 Actions
References
Testing
Checklist
CONTRIBUTING.md.