I had plans to extract the web application from contacts-mobile-basic and contacts-mobile-secured into contacts-mobile-webapp, so that there would only be one webapp in the code base. That would have enabled us to configure a single webapp to work against any of the three backends:1. contacts-mobile-basic2. contacts-mobile-picketlink-secured3. contacts-mobile-proxyBut after looking closer I think it might make more sense to leave contacts-mobile-basic as-is, and let contacts-mobile-webapp work against contacts-mobile-picketlink-secured and contacts-mobile-proxy. This is due to the security pages/links etc that have no backend support in contacts-mobile-basic.
The current state of things is that I've extracted the webapp from contacts-mobile-picketlink-secured into contacts-mobile-webapp and tested it against contacts-mobile-picketlink-secured and contacts-mobile-proxy and things work as expected [1].I need a fabric8-1.1.0.Beta7 before I can issue a PR for this but it would be great if anyone has time to tryout the branch below and see if we can discover any additional issue.
_______________________________________________On 26 May 2014 16:00, Daniel Bevenius <daniel.bevenius@gmail.com> wrote:
I think I've got the delete sorted with this commit:On 26 May 2014 14:14, Daniel Bevenius <daniel.bevenius@gmail.com> wrote:
I'm seeing an issue with deleting of a contact...If I log in as user 'admin' and delete a contact, the next screen the deleted user is still in the list of contacts. If I then go to the "List View" the user is gone.On 26 May 2014 12:02, Matthias Wessendorf <matzew@apache.org> wrote:
On Mon, May 26, 2014 at 11:57 AM, Daniel Bevenius <daniel.bevenius@gmail.com> wrote:
Hey ChristosI've seen a few of these and perhaps all. I'm currently working on extracting the webapp into a separate project/modules named contacts-mobile-webapp. The webapp in that module was extracted from contacts-mobile-picketlink-secured and I've made some modifications.+1 awesome!For the logout issue I had to add the following:This was to make the CORSFilter happy or it would consider the request invalid.I've also seen the 403 Forbidden messages but I'm no longer able to reproduce them. I'll take another look at this though.On 26 May 2014 11:29, Christos Vasilakis <cvasilak@gmail.com> wrote:Hi all,
during the development of the iOS contacts client [1] , came across the following issues on the web interface. (Note: I am using edewit [2] branch that contains the Push functionality).
a) Login with “duke:duke" (role.MAINTAINER) and try to edit(PUT) an existing contact you get back a 403-Forbidden message.
b) Login with “admin:admin (role.ADMIN) and try to delete(DELETE) an existing contact you get back a 403-Forbidden message.
Interestingly enough, on the iOS client using the same credentials in the above scenarios, they work correctly.. so possible(?) there are some issues on the web interface.
c) Logout on the web interface gives back a “Forbidden” message.
Tested on both wildfly-8.1.0.CR1 / CR2 and JBoss- EAP-6.2
Let me know if these are currently worked on or you want me to create JIRA’s.
Thanks,
Christos
[1] https://github.com/aerogear/aerogear-push-quickstarts/pull/3
[2] https://github.com/edewit/jboss-wfk-quickstarts/tree/push/contacts-mobile-picketlink-secured
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev