Modify ↓
Opened 13 years ago
Closed 13 years ago
#9507 closed defect (fixed)
Authentication for CollabNet Security Realm
| Reported by: | Owned by: | roadrunner | |
|---|---|---|---|
| Priority: | normal | Component: | HudsonTracPlugin |
| Severity: | normal | Keywords: | j_acegi_security_check |
| Cc: | Trac Release: | 0.11 |
Description (last modified by )
Here is the error even with the correct 'username' and 'password' in the trac.ini [hudson] section where the continuous integration machine is using CollabNet Security Realm:
Event provider HudsonTracPlugin failed for filters "Hudson Builds":
IOError: Error getting build info from 'http://localhost:8080/job/Build/api/python?tree=builds[building,timestamp,duration,result,description,url,fullDisplayName,changeSet[items[revision,id]]],modules[builds[building,timestamp,duration,result,description,url,fullDisplayName,changeSet[items[revision,id]]]]': returned document has unexpected type 'text/html' (expected 'text/x-python'). The returned text is: <html><head><meta http-equiv='refresh' content='1;url=/login?from=%2Fjob%2FBuild%2Fapi%2Fpython'/><script>window.location.replace('/login?from=%2Fjob%2FBuild%2Fapi%2Fpython');</script></head><body style='background-color:white; color:white;'>Authentication required</body></html>
Attachments (0)
Change History (3)
comment:1 Changed 13 years ago by
| Description: | modified (diff) |
|---|
comment:2 Changed 13 years ago by
comment:3 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
I'm not familiar with the CollabNet security realm. But I'm guessing the the server is not returning a proper error status code - can you verify what http status code is being returned when you access the URL in the error message? (either snooping, or using something like lwp-request that can be told to show the response status code).
If you're running, or willing to upgrade to, Jenkins 1.426 or later, then I could add support for using the API Token approach (https://wiki.jenkins-ci.org/display/JENKINS/Authenticating+scripted+clients) which I think might solve your issue.