jpf/super-widget

Single Page Application that demonstrates the Okta Sign-In Widget

super-widget's Issues

Add post-login token viewer

Zee's demo has a slick token viewer UI that needs to get ported over to this code.

Handle errors that show up GET parameters

For example, the code should be able to handle URLs like this one:

http://localhost:4000/?state=rjytMZuvhnUAihivSBdl0r9vGBb1nKLXPfJphQ0TD20axPisTqOdD7YV76VcdUvD&error=unsupported_response_type&error_description=The+response+type+is+not+supported+by+the+authorization+server.+Configured+response+types:+%5Btoken,+id_token%5D

Change ID used in renderEl to point at the more common "okta-login-container" ID

To allow for easier cut-and-pasting of example code, change this: signInWidget.renderEl({el: '#nav-home-tab-widget'}) to signInWidget.renderEl({el: '#okta-login-container'}) - this necessarily depends on issue #1

Instructions - Jekyll version collision

Ran into an issue with the instructions on the readme. I think the install guide needs to start with only installing bundler, and then move into the project directory to install jekyll. Installing jekyll globally will install the latest version, colliding with that found in the gem.lockfile.

Does that sound right? I can submit a PR for the change but want to ensure we're aligned.

Update to responsive design

This code should work, and look good, on mobile devices.

Port project to Vue.js and remove need for Jekyll

This project depends on Jekyll for creation of static files. With the use of Vue.js, we should be able to remove that dependency entirely.

Goals:

• Instead of writing JS and SASS configuration into index.html and then re-reading those files for dynamic features. Use Vue.js to do this the same way on default load, or when using custom configuration.
• One of the primary uses of Jekyll is parameterizing configuration variables. These should instead be defined in JS and "bound" (using whatever Vue.js calls "databinding") to the configuration and loading of the configuration (hopefully, a side-effect of this is that configuration of custom variables is handed "for free" by Vue.js)

Likely challenges:

• The code is littered with gross setTimeout hacks, a redesign should remove as many setTimeout hacks as possible
• Currently, this code instantiates 7 instances CodeMirror and manages the updates of all of them. Hopefully moving to Vue.js will allow us to just manage 2 (letting Vue.js handle updates to the contents of the editors)
• CodeMirror can have issues if it is instantiated when it isn't visible. This might require some effort to make it work with Vue.js

Add IDP Discovery functionality

Add SAML IdP ID functionality

showPasswordToggleOnSignInPage: false not working

Sign in widget support: showPasswordToggleOnSignInPage: false which will hide password. This is used in some socail logins as Okta password is not used there.

When this key is put into the text box, password box remains, so it would be nice thing to support too

Good job on an app, really like it!

Update post-login view to make it clear that you're logged in

Use message on the order of:

Hello ____, you are now logged in!