[
https://issues.apache.org/jira/browse/WOOKIE-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Wilson updated WOOKIE-283:
--------------------------------
Affects Version/s: (was: 0.9.2)
0.9.1
Fix Version/s: (was: 0.9.2)
0.9.1
This was actually fixed in 0.9.1
> Logging into admin interface inteferes with API calls
> -----------------------------------------------------
>
> Key: WOOKIE-283
> URL: https://issues.apache.org/jira/browse/WOOKIE-283
> Project: Wookie
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.9.1
> Reporter: Ross Gardler
> Assignee: Scott Wilson
> Priority: Blocker
> Fix For: 0.9.1
>
>
> If a widget consumes a REST service then everything works fine until the same
> browser logs into the Wookie admin service. After this calling the REST API
> results in a login challenge. This is 100% reproduceable as follows
> Preparation:
> - you need a fresh browser on which you have *not* logged into the admin
> console
> - deploy the template test widgets: cd widgets/templates; ant
> generate-test-widgets
> - visit the "Browse Test Widget"
> - everything should work fine
> Reproduce the problem:
> - log into the wookie admin interface
> - visit the Browse Test Widget
> - you will be asked to login
> The weather widget (which also makes a proxied request) works fine. I can
> only assume that this indicates a difference in the interaction styles. The
> weather widget simply consumes an RSS feed, the twitter widgets consume a
> REST service.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
