Hi @edunham,
We also need to migrate our OIN integration to my new Integrator Free Plan. Can you please DM me the address for opening a support case?
Hi, I am trying to migrate my dev account with 4 users, 2 groups, and a handful of SAML and OIDC apps to my new integration account. I installed go, the okta cli client and envsync.
I have go added to my PATH var of my user’s profile as well as the okta cli and envsync.
The test for the okta cli client however, does not show the global flags config section.
On running envsync for backup, all of it errors out with warning messages of “unknown flag: --config.”
I have verified go is in the PATH. I have my API tokens for my dev Okta account saved inside ~/.okta/okta.yaml.
This is on a Amazon Linux VM.
What am I doing wrong? I am not an expert in Go.
I am unable to find documentation on how to triage this or how to open a support case to get some help. Please help.
Hi @edunham or someone else from the Okta Team,
Can you please DM us the address for opening a support case for migrating our OIN integration to our new Integrator Free Plan?
If you have only a few identity providers (Single Sign-On) in Okta prices (6$/user) are way to high for something that can also be configured with open source software (e.g. Keycloak). Sorry to let you go Okta.
@edunham @oktadev-blog Can you please confirm if oktapreview dev accounts will also be deprecated with these changes? For example, my domain looks like https://dev-123456-admin.oktapreview.com. In my admin portal, I do see the text “Developer Edition provides a limited number of apps.” under Applications → Applications. However, I found a conflicting comment on GitHub by edunham that states “preview is unaffected by the deprecation”.
@codas it’s likely the version of the okta-cli-client is wrong. You’ll need the one in the README instructions GitHub - oktadev/okta-dev-account-migration-tool
@edunham @oktadev-blog Based on the notes, this only impacts accounts that shows the warning of application limit. We haven’t seen that warning—likely because Okta Support and our CSM previously helped us clear those limits, and we’ve been using the tenants extensively for Development and QA.
Do you know if tenants with URLs like dev-{digits}.oktapreview.com are affected? I’m not seeing any application limit warnings on them.
Are there any limits to the count of applications in Integrator Free accounts? Previously, dev accounts were limited to 5 apps.
Not able to figure out how to set a password-only sign-on policy for a App using the free integrator version. Would like to use this to drive a playwright test of our app configured as an OIDC application. Can do this with older free dev account.
When I try to set this password-only poicy it tried to do “Step up authentication” but I don’t find any UI to enter the Okta Verify code (which I was expecting would be the “stup up authentication”). Rather it just continues to display an error saying Step up authentication is required.
Is there some other way to configure an App to just use password authentication?
Hi all, we tried logging in today and got the message “This developer org has been deactivated. If you need access or have questions, please contact your org admin.”. I am the admin, i got no email warning that this was going to happen. Is it too late to migrate to the new system?
I’m in this boat as well. Got deactivated today, but no warning! What am I able to do to migrate??
Hello,
My account was suspended without any prior warning.
I’m in great trouble.
I sent an email to developers@okta.com earlier, so please check it as soon as possible.
This also happened to me, and of course the support@ address is deprecated. Really disappointing there was no email notice or notice on the org dashboard, but I’m honestly not surprised having used Okta in prod at my companies and dealing with their support.
We also got deactivated without warning! Any luck with accessing/migrating old data?
I’m sorry that this has been a frustrating experience! All affected accounts showed banners in the admin dashboards, which we hoped would be conspicuous during the kind of tasks that developer accounts were designed for. I wish we’d been able to email everybody, but the quantity of developer accounts involved made that infeasible.
If your dev org was associated with a production org, please contact Okta support through the production org and provide the ID of your dev org.
If your dev org was being used as a production org and you don’t have a production org yet, please contact sales through Contact Sales | Okta to explore your options. Account reps have a few options for retrieving configuration and data from dev orgs that were being used as prod orgs, but unfortunately those are only available to customers.
If you have an OIN integration that was created from your dev org, please create an integrator org and email developers@okta.com to get help migrating your integration.
For dev orgs that were only used for testing, you can point any setup tooling at an integrator org and re-run it. OIE dev orgs and integrator orgs have identical APIs, though the 10 active user cap in integrator accounts may mean you need to create some test users as inactive.
Also hit with no warning about this change, not very good form when the original intent was to get developers into the ecosystem for wider applications. I’ve since reworked to a magiclink approach as that will suffice for our needs.
The communication of this change was very disappointing, hope you take that onboard.
A blanket email should be sent out to all affected parties as its a bad time to find out your Authentication is broken when a user tries to log back in after a session expiry.