Originals Access Okta Sign-In & Accounts

This guide helps you sign in with Okta single sign-on (SSO) to access your studio applications and cloud workstation, and walks through common login, password, and multi-factor authentication (MFA) issues. Try the self-service steps below first, then reach out to TechOps at support@amazonstudios.com if you're still stuck.

I can't log in with Okta. What do I do?

1. Confirm you're using the correct username/email and that Caps Lock is off.
2. Try signing in again, temporary glitches often clear on a second attempt.
3. If you see a message that your account has expired or is deactivated, it may have lapsed due to inactivity, email TechOps at support@amazonstudios.com to have it reactivated (see "When to contact support" below).

How do I reset my Originals Access/Okta password?

1. Go to https://login.originalsaccess.com/ and try logging in there.
2. On the password screen, choose "Forgot password?" and follow the steps in the reset email you receive.
3. Use your organization's official password-reset link if one has been provided to you, and choose a password that meets the listed requirements.
4. Allow a few minutes for the reset email or verification code to arrive, and check your spam/junk folder.
5. If no email or code arrives, or your new password keeps getting rejected even though it meets the requirements, contact TechOps at support@amazonstudios.com for a manual reset (see below).

My multi-factor authentication (MFA) isn't working / I got a new phone. What now?

If you have a new, lost, broken, or reset phone, or you deleted and reinstalled your authenticator app, your old MFA enrollment no longer works and needs to be reset. Email TechOps at support@amazonstudios.com to have your MFA enrollment reset, then re-enroll by scanning the new QR code in the authenticator app on your current device. After re-enrolling, complete the MFA prompt and sign in again to confirm it works.

I signed into the web portal, but my cloud workstation client won't connect. Why?

1. Confirm you can sign in to the web portal but the workstation/remote desktop client fails, and note the exact error message (for example, "Invalid username, password, or token").
2. Check how you're entering your username: HP Anyware uses only the username portion of your account, not the full email. Enter just the part before @ (e.g. name), not name@originalsaccess.com. The full email works on the web portal but will fail in the HP Anyware client. For more on the client itself, see Cloud Workstations (HP Anyware / PCoIP).
3. Reset your password and confirm your MFA/authenticator is enrolled and working, then try the client again.
4. If it still fails after your password and MFA are confirmed good, contact ProdTech at post-support@amazonstudios.com with the exact client error so they can check your account and connection on the back end.

I'm locked out of my account. How do I get back in?

Email TechOps (TOPS) at support@amazonstudios.com for assistance.

When to contact support

If the self-service steps above don't resolve your issue, reach out to the team that handles your type of request:

ProdTech, post-support@amazonstudios.com

ProdTech manages Studio in the Cloud, including initial user onboarding, new account creation, and provisioning access to storage, workspaces, cloud workstations, applications, and tools, plus the setup, performance, and technical issues covered in this guide.

TechOps (TOPS), support@amazonstudios.com

TechOps manages your Originals Access account, and will assist you with issues around Okta sign-in/SSO problems, password resets, MFA/2FA resets (including a new phone), and account lockouts.

TechOps also handles requests for access to specific applications (such as Box, Flow Capture, or Aspera on Cloud).

When contacting us, help us resolve your issue quickly by always including:

• Your full name and account email (@originalsaccess.com).
• A clear description of the problem and the exact error message you see (a screenshot helps).
• Your show code and show name.
• The show/workspace, workstation, or application involved.
• When the problem started and what you've already tried.

Please open a new request for each separate issue rather than replying to an older, resolved one, so it reaches the right team.