# Redirect to Login or Application After Activation

**URL:** <https://devforum.okta.com/t/redirect-to-login-or-application-after-activation/783>\
**Category:** OAuth/OIDC\
**Created:** [November 20, 2017, 4:07am UTC](https://devforum.okta.com/t/redirect-to-login-or-application-after-activation/783 "2017-11-20T04:07:20Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![tom](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/tom/32/24_2.png) [@tom](https://devforum.okta.com/u/tom)\
**Post date:** [March 15, 2018, 10:45pm UTC](https://devforum.okta.com/t/redirect-to-login-or-application-after-activation/783/7 "2018-03-15T22:45:56Z")

</div>

This is getting a lot of heat. Let me talk about how you can do this today. I should have put this information in here before, I left out the information on what you need to do to the email.

There is another email macro you can use, I think y’all are aware of `${activationLink}`, there is also `${activationToken}`.

With this, you can modify the activation email to point to your own application:

```auto
https://myapplication.com/activate?token=${activationToken}

```

After your application gets the token, you can activate the user by an API call: [Primary authentication with activation token](https://developer.okta.com/docs/api/resources/authn#primary-authentication-with-activation-token)

From here, you can get the `sessionToken` and exchange it for an `id_token` and/or `access_token` as normal using the authorization route:

[https://developer.okta.com/docs/api/resources/oidc#authorize](https://developer.okta.com/docs/api/resources/oidc#authorize)

Let me know any questions about this, we are still working on pulling our email verification and activation APIs so they can work correctly for OIDC flows. This is the workaround we have for now

---

_[View the full topic](https://devforum.okta.com/t/redirect-to-login-or-application-after-activation/783)._