Hi, we are using self-registration from multiple applications. However, there does not appear to be a way to save which application the user registered from in their profile.
Is there a way to do that?
Hi ,
There’s no native way to capture the originating app at self-registration, but here’s a workable approach using the Registration Inline Hook.
Approach: Map enrollment policy rule ID to app name
The registration inline hook payload includes a source field with the rule ID of the enrollment policy that triggered it. If each app has its own enrollment policy, that rule ID uniquely identifies the app your hook service can map it to an app name and write it back to the user profile before activation.
Setup:
1. Ensure each app has its own enrollment policy (apps on a shared policy cannot be distinguished with this method)
2. Add a custom profile attribute (e.g., registrationSource) to your Universal Directory schema
3. Build a registration inline hook endpoint that:
- Reads the rule ID from the hook payload
- Maps it to the corresponding app name
- Returns a com.okta.user.profile.update command:
{
"commands": [
{
"type": "com.okta.user.profile.update",
"value": { "registrationSource": "MyAppName" }
},
{
"type": "com.okta.action.update",
"value": { "registration": "ALLOW" }
}
]
}
Limitations:
- Enrollment policies are only works in OIE org.
- If multiple apps share a policy, this won’t work. The fallback is an Okta Workflows flow triggered on user.lifecycle.create to capture and write app context post-registration.