Debugging interactive app launch

[jeff.ohrstrom]

@mcuma

if I push the “Connect to Jupyter” again, the Jupyter gets launched. So, something is blocking the first push, but lets through the second.

Do you use Shibboleth authentication? This sounds like a CASScope issue.

Jupyter app ask for password first time, works second time

OK forget the authentication bit. It looks like you’re correctly passing auth in the first request. Let’s now assume it’s a problem with redirection and maybe setting and passing cookies. Sorry it took this long to get here. Here is what a correct redirection flow is. Notice the status codes received from login and 55808 are 302 Found. [image] Seems that your 302 redirects are not working the first time? Here’s what my very first 302 redirect response looks like. See the locaion is rela…

In terms of debugging - you’re web client is your best bet for this situation - it’ll tell you what’s going on - where you’re being redirected to (if it’s the right location with the right credentials and so on).