# Create Activated User without Credentials Flow issue okta api **URL:** \ **Category:** API\ **Tags:** api\ **Created:** [January 24, 2018, 8:30am UTC](https://devforum.okta.com/t/create-activated-user-without-credentials-flow-issue-okta-api/1109 "2018-01-24T08:30:58Z")\ **Posts on this page:** 1\ **Showing post:** 9
**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 27, 2018, 4:25pm UTC](https://devforum.okta.com/t/create-activated-user-without-credentials-flow-issue-okta-api/1109/9 "2018-03-27T16:25:07Z")
I believe if you are searching for something to get out the door in the month, the workaround mentioned in: > [@Redirect to Login or Application After Activation](https://devforum.okta.com/t/redirect-to-login-or-application-after-activation/783): > > How do you configure activation to redirect either to login or back to your application after successfully activating a user account from the email? I don’t see any ability to configure the flow or functionality? is the only option. I have a question for you, are you OK collecting the password upfront? The registration as a service feature, if you can collect the password upfront will behave the way that you expect, you will be able to either require or defer email verification, but it will require that you collect the primary credential up front. This feature, in particular, is on our short-term roadmap, and the team is currently working on it. We are currently tracking towards ~ Oktane '18, but _please remember, dates can change._ You can watch [https://support.okta.com/help/OktaProductRoadMap](https://support.okta.com/help/OktaProductRoadMap), this feature is called Self-Service Registration. Hope this helps, Tom --- _[View the full topic](https://devforum.okta.com/t/create-activated-user-without-credentials-flow-issue-okta-api/1109)._