Throw error if configured with a scope string instead of array

[aaronpk]

I'm submitting a

• [ ] bug report
• [X] feature request

Background info

Previous versions allowed this to be configured with string values of scope, e.g. scope: 'openid email'. Now, the values need to be an array, e.g. scopes: ['openid', 'email'].

Expected behavior

Configuring the widget with a string value should throw an error, since this will not work. This is especially important when someone is upgrading from a previous version of the widget.

What went wrong?

Instead, the widget hangs after the user enters their credentials, no error is in the console, and no tokens are returned. Since there is no error visible in the console or anywhere else, there is no clear indication that this was the source of the problem.

Steps to reproduce

• Configure the widget with scopes: 'openid email'
• Attempt to log in

Your environment

• Okta Sign-In Widget Version: 5.9.4
• Browser: Chrome
• OS: Mac
• Language: JavaScript

[denysoblohin-okta]

Thanks for pointing on this issue Internal ref: https://oktainc.atlassian.net/browse/OKTA-433743