[jbosstools-issues] [JBoss JIRA] (JBIDE-17453) Error while validating credentials in Download Runtime dialog

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-17453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972568#comment-12972568 ] 

Rob Stryker commented on JBIDE-17453:
-------------------------------------

So the jdf download manager rest api is not documnented properly. In fact its documentation is very sparse, though the official download manager rest api is properly documented (no /jdf in the url). 

It seems it is returning status 200 when the credentials are correct but the workflow has not been completed, ie, user did not yet sign t&c.  I was expecting a 403 in this case.

What makes it more confusing, though, is that some of you guys seem able to get to the t&c page without issue, which means the rest service must somehow be alternating between 200 or 403.

My attempts via curl show a status of 200 is always returned if the credentials are correct and user did not sign t&c. 

For now, I'm going to allow either a 403 or a 200 to mean the t&c has not yet been signed. I will also push this to master and beta2. 

> Error while validating credentials in Download Runtime dialog
> -------------------------------------------------------------
>
>                 Key: JBIDE-17453
>                 URL: https://issues.jboss.org/browse/JBIDE-17453
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: runtime-detection
>    Affects Versions: 4.2.0.Beta2
>            Reporter: Radoslav Rábara
>            Assignee: Rob Stryker
>            Priority: Blocker
>              Labels: respin-a
>             Fix For: 4.2.0.Beta2
>
>         Attachments: credentials validation error.jpg
>
>
> After validation of valid credentials, the following error message appears
> {code}
> "An error occured while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 200"
> {code}
> I was able to reproduce this issue only with one of mine jboss.org accounts.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)