[ https://issues.jboss.org/browse/JBIDE-19786?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19786 at 5/11/15 12:10 PM: -------------------------------------------------------------------- discussing this in #openshift-dev-ui unveils that stg server is backed by oauth that's handled in the browser: {quote} (06:05:20 PM) liggitt: if the token request sends back a www-authenticate challenge, you can handle it like you are today (06:05:34 PM) liggitt: if it doesn't, it sends back a message of where to go (06:05:51 PM) liggitt: osc is just displaying the returned content (06:05:54 PM) jcantril: liggitt: you probably told me all o fthis before (06:05:58 PM) liggitt: you get back a 401 with no www-challenge header (06:08:39 PM) liggitt: 401 without www-challenge means you need a token, but can't get it in an automated way (06:08:42 PM) liggitt: that's the google oauth case (06:09:18 PM) liggitt: in that case, show them the body of the response... we're including messages and a link to where they get the token {quote} osc is handling this by showing the message that's being presented instead of the www-challenge header. was (Author: adietish): discussing this in #openshift-dev-ui unveils that stg server is backed by oauth that's handled in the browser: {quote} (06:05:20 PM) liggitt: if the token request sends back a www-authenticate challenge, you can handle it like you are today (06:05:34 PM) liggitt: if it doesn't, it sends back a message of where to go (06:05:51 PM) liggitt: osc is just displaying the returned content (06:05:54 PM) jcantril: liggitt: you probably told me all o fthis before (06:05:58 PM) liggitt: you get back a 401 with no www-challenge header {quote} osc is handling this by showing the message that's being presented instead of the www-challenge header. -- This message was sent by Atlassian JIRA (v6.3.15#6346)