From edewit at redhat.com Mon Aug 3 03:21:09 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Mon, 3 Aug 2015 09:21:09 +0200 Subject: [Aerogear-users] notifications overriding previus ones, Cordova Android In-Reply-To: References: Message-ID: Hi This is doable, on android you have a lot of freedom how to display the messages in the notifications panel. Right now we've opted having more or less the same functionally as on iOS, but we could add this I've create an issue for it: https://issues.jboss.org/browse/AGCORDOVA-113 If your interested in adding this yourself you should take a look at https://github.com/aerogear/aerogear-cordova-push/blob/master/src/android/org/jboss/aerogear/cordova/push/NotificationMessageHandler.java That is where the notification is put into the Notification panel. On Fri, Jul 31, 2015 at 1:53 PM, Jes?s Mart?n Gonz?lez < jesus90martin at gmail.com> wrote: > Hi all, > > How can I show all the notifications received?, not only the last one. > Something like whatsapp notifications, when there are 2 notifications, both > are showed at notifications panel and not only the last one. > > Using Cordova Android and your Pushplugin > > thanks > > -- > Jes?s Mart?n Gonzalez > Tel: +34 654420529 > > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150803/3a6b643c/attachment-0001.html From fabio.turizo at gmail.com Wed Aug 5 10:30:03 2015 From: fabio.turizo at gmail.com (Fabio Turizo) Date: Wed, 05 Aug 2015 14:30:03 +0000 Subject: [Aerogear-users] Aerogear Unified Push Server setup not working Message-ID: Greetings. I've followed all instrucciones detailed in the AeroGear UPS Installation Guide but the server isn't working. My setup is done in an AWS instance running with RHEL 7 installing Aerogear UPS v1.0.3 with a PostgreSQL 9.4 database (via AWS RDS) and using WildFly 8.2.1 Final with Oracle JDK 8 When i deploy the WARs (agpush and auth) everything is deployed fine. Trying to get in the admin ui gets me an Internal error. Checking the logs: *2015-08-05 10:11:08,832 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ag-push/index.html: java.lang.RuntimeException: Can't resolve relative url from adapter config.* * at org.keycloak.adapters.AdapterDeploymentContext.getBaseBuilder(AdapterDeploymentContext.java:289) [keycloak-adapter-core-1.0.5.Final.jar:]* * at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:53) [keycloak-adapter-core-1.0.5.Final.jar:]* * at org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:54) [keycloak-undertow-adapter-1.0.5.Final.jar:]* * at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)* * at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.0.5.Final.jar:]* * at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.0.5.Final.jar:]* * at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51]* * at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51]* * at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]* Is there a configuration missing in the setup that causes this error? Any help is appreciated. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150805/5ccb33ff/attachment.html From kelvin at qantel.com Wed Aug 5 18:13:05 2015 From: kelvin at qantel.com (Kelvin Lunsford) Date: Wed, 5 Aug 2015 22:13:05 +0000 Subject: [Aerogear-users] Aerogear Unified Push Server setup not working In-Reply-To: References: Message-ID: <701caecae51a4c37845a119959c86b51@stantz.qantel.com> The error is because ssl is required. By default the https protocol scheme is required to access the UPS console when not using localhost as the URL host name. Https is not required for localhost access to the console. You might see if you can tunnel into your AWS instance as localhost. You will eventually need a cert and https connector configured in wildfly to access the restful interfaces. - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Fabio Turizo Sent: Wednesday, August 05, 2015 7:30 AM To: aerogear-users at lists.jboss.org Subject: [Aerogear-users] Aerogear Unified Push Server setup not working Greetings. I've followed all instrucciones detailed in the AeroGear UPS Installation Guide but the server isn't working. My setup is done in an AWS instance running with RHEL 7 installing Aerogear UPS v1.0.3 with a PostgreSQL 9.4 database (via AWS RDS) and using WildFly 8.2.1 Final with Oracle JDK 8 When i deploy the WARs (agpush and auth) everything is deployed fine. Trying to get in the admin ui gets me an Internal error. Checking the logs: 2015-08-05 10:11:08,832 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ag-push/index.html: java.lang.RuntimeException: Can't resolve relative url from adapter config. at org.keycloak.adapters.AdapterDeploymentContext.getBaseBuilder(AdapterDeploymentContext.java:289) [keycloak-adapter-core-1.0.5.Final.jar:] at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:53) [keycloak-adapter-core-1.0.5.Final.jar:] at org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:54) [keycloak-undertow-adapter-1.0.5.Final.jar:] at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.0.5.Final.jar:] at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.0.5.Final.jar:] at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) [undertow-core-1.1.8.Final.jar:1.1.8.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] Is there a configuration missing in the setup that causes this error? Any help is appreciated. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150805/62be847a/attachment-0001.html From fabio.turizo at gmail.com Thu Aug 6 10:05:07 2015 From: fabio.turizo at gmail.com (Fabio Turizo) Date: Thu, 06 Aug 2015 14:05:07 +0000 Subject: [Aerogear-users] Aerogear Unified Push Server setup not working In-Reply-To: <701caecae51a4c37845a119959c86b51@stantz.qantel.com> References: <701caecae51a4c37845a119959c86b51@stantz.qantel.com> Message-ID: Ok, i configured the HTTPS listener for the server and now the application works as intended. Many thanks! El mi?., 5 de ago. de 2015 a la(s) 5:13 p. m., Kelvin Lunsford < kelvin at qantel.com> escribi?: > The error is because ssl is required. > > > > By default the https protocol scheme is required to access the UPS console > when not using localhost as the URL host name. > > > > Https is not required for localhost access to the console. You might see > if you can tunnel into your AWS instance as localhost. > > > > You will eventually need a cert and https connector configured in wildfly > to access the restful interfaces. > > > > - Kelvin > > > > > > *From:* aerogear-users-bounces at lists.jboss.org [mailto: > aerogear-users-bounces at lists.jboss.org] *On Behalf Of *Fabio Turizo > *Sent:* Wednesday, August 05, 2015 7:30 AM > *To:* aerogear-users at lists.jboss.org > *Subject:* [Aerogear-users] Aerogear Unified Push Server setup not working > > > > Greetings. I've followed all instrucciones detailed in the AeroGear UPS > Installation Guide but the server isn't working. > > > > My setup is done in an AWS instance running with RHEL 7 installing > Aerogear UPS v1.0.3 with a PostgreSQL 9.4 database (via AWS RDS) and using > WildFly 8.2.1 Final with Oracle JDK 8 > > > > When i deploy the WARs (agpush and auth) everything is deployed fine. > Trying to get in the admin ui gets me an Internal error. Checking the logs: > > > > *2015-08-05 10:11:08,832 ERROR [io.undertow.request] (default task-1) > UT005023: Exception handling request to /ag-push/index.html: > java.lang.RuntimeException: Can't resolve relative url from adapter config.* > > * at > org.keycloak.adapters.AdapterDeploymentContext.getBaseBuilder(AdapterDeploymentContext.java:289) > [keycloak-adapter-core-1.0.5.Final.jar:]* > > * at > org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:53) > [keycloak-adapter-core-1.0.5.Final.jar:]* > > * at > org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:54) > [keycloak-undertow-adapter-1.0.5.Final.jar:]* > > * at > io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)* > > * at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) > [keycloak-undertow-adapter-1.0.5.Final.jar:]* > > * at > org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) > [keycloak-undertow-adapter-1.0.5.Final.jar:]* > > * at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* > > *at > io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) > [undertow-core-1.1.8.Final.jar:1.1.8.Final]* > > * at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [rt.jar:1.8.0_51]* > > * at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [rt.jar:1.8.0_51]* > > * at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]* > > > > Is there a configuration missing in the setup that causes this error? Any > help is appreciated. > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150806/00155906/attachment.html From fabio.turizo at gmail.com Thu Aug 6 10:57:04 2015 From: fabio.turizo at gmail.com (Fabio Turizo) Date: Thu, 06 Aug 2015 14:57:04 +0000 Subject: [Aerogear-users] Aerogear Unified Push Server setup not working In-Reply-To: References: <701caecae51a4c37845a119959c86b51@stantz.qantel.com> Message-ID: Well, still have issues with the admin application. I'm getting this *Error 401: Unathorized errors* in the admin interface. I work for a minute or two in the application and get the error, log out of the application/refresh browser and again after one or two minutes happens again. Quite annoying. Checking the server logs i see this exception: *2015-08-06 10:50:19,297 ERROR [org.keycloak.adapters.BearerTokenRequestAuthenticator] (default task-4) Failed to verify token: org.keycloak.VerificationException: Token* *is not active.* * at org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:43) [keycloak-core-1.0.5.Final.jar:]* * at org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:16) [keycloak-core-1.0.5.Final.jar:]* * at org.keycloak.adapters.BearerTokenRequestAuthenticator.authenticate(BearerTokenRequestAuthenticator.java:63) [keycloak-adapter-core-1.0.5.Final.jar:]* * at org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:41) [keycloak-adapter-core-1.0.5.Final.jar:]* * at org.keycloak.adapters.undertow.UndertowKeycloakAuthMech.keycloakAuthenticate(UndertowKeycloakAuthMech.java:82) [keycloak-undertow-adapter-1.0.5.Final.jar:]* * at org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:61) [keycloak-undertow-adapter-1.0.5.Final.jar:]* * at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)* * at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.0.5.Final.jar:]* * at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.0.5.Final.jar:]* * at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51]* * at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51]* * at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]* *2015-08-06 10:51:51,799 ERROR [org.keycloak.adapters.BearerTokenRequestAuthenticator] (default task-14) Failed to verify token: org.keycloak.VerificationException: Token is not active.* * at org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:43) [keycloak-core-1.0.5.Final.jar:]* * at org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:16) [keycloak-core-1.0.5.Final.jar:]* * at org.keycloak.adapters.BearerTokenRequestAuthenticator.authenticate(BearerTokenRequestAuthenticator.java:63) [keycloak-adapter-core-1.0.5.Final.jar:]* * at org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:41) [keycloak-adapter-core-1.0.5.Final.jar:]* * at org.keycloak.adapters.undertow.UndertowKeycloakAuthMech.keycloakAuthenticate(UndertowKeycloakAuthMech.java:82) [keycloak-undertow-adapter-1.0.5.Final.jar:]* * at org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:61) [keycloak-undertow-adapter-1.0.5.Final.jar:]* * at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)* * at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.0.5.Final.jar:]* * at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.0.5.Final.jar:]* * at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) [undertow-core-1.1.8.Final.jar:1.1.8.Final]* * at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51]* * at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51]* * at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]* El jue., 6 de ago. de 2015 a la(s) 9:02 a. m., Fabio Turizo < fabio.turizo at gmail.com> escribi?: > Ok, i configured the HTTPS listener for the server and now the application > works as intended. Many thanks! > > El mi?., 5 de ago. de 2015 a la(s) 5:13 p. m., Kelvin Lunsford < > kelvin at qantel.com> escribi?: > >> The error is because ssl is required. >> >> >> >> By default the https protocol scheme is required to access the UPS >> console when not using localhost as the URL host name. >> >> >> >> Https is not required for localhost access to the console. You might see >> if you can tunnel into your AWS instance as localhost. >> >> >> >> You will eventually need a cert and https connector configured in wildfly >> to access the restful interfaces. >> >> >> >> - Kelvin >> >> >> >> >> >> *From:* aerogear-users-bounces at lists.jboss.org [mailto: >> aerogear-users-bounces at lists.jboss.org] *On Behalf Of *Fabio Turizo >> *Sent:* Wednesday, August 05, 2015 7:30 AM >> *To:* aerogear-users at lists.jboss.org >> *Subject:* [Aerogear-users] Aerogear Unified Push Server setup not >> working >> >> >> >> Greetings. I've followed all instrucciones detailed in the AeroGear UPS >> Installation Guide but the server isn't working. >> >> >> >> My setup is done in an AWS instance running with RHEL 7 installing >> Aerogear UPS v1.0.3 with a PostgreSQL 9.4 database (via AWS RDS) and using >> WildFly 8.2.1 Final with Oracle JDK 8 >> >> >> >> When i deploy the WARs (agpush and auth) everything is deployed fine. >> Trying to get in the admin ui gets me an Internal error. Checking the logs: >> >> >> >> *2015-08-05 10:11:08,832 ERROR [io.undertow.request] (default task-1) >> UT005023: Exception handling request to /ag-push/index.html: >> java.lang.RuntimeException: Can't resolve relative url from adapter config.* >> >> * at >> org.keycloak.adapters.AdapterDeploymentContext.getBaseBuilder(AdapterDeploymentContext.java:289) >> [keycloak-adapter-core-1.0.5.Final.jar:]* >> >> * at >> org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:53) >> [keycloak-adapter-core-1.0.5.Final.jar:]* >> >> * at >> org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:54) >> [keycloak-undertow-adapter-1.0.5.Final.jar:]* >> >> * at >> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)* >> >> * at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >> [keycloak-undertow-adapter-1.0.5.Final.jar:]* >> >> * at >> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >> [keycloak-undertow-adapter-1.0.5.Final.jar:]* >> >> * at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* >> >> *at >> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final]* >> >> * at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >> [rt.jar:1.8.0_51]* >> >> * at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >> [rt.jar:1.8.0_51]* >> >> * at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51]* >> >> >> >> Is there a configuration missing in the setup that causes this error? Any >> help is appreciated. >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150806/ebbc913c/attachment-0001.html From kelvin at qantel.com Thu Aug 6 16:24:00 2015 From: kelvin at qantel.com (Kelvin Lunsford) Date: Thu, 6 Aug 2015 20:24:00 +0000 Subject: [Aerogear-users] Aerogear Unified Push Server setup not working In-Reply-To: References: <701caecae51a4c37845a119959c86b51@stantz.qantel.com> Message-ID: <5347cb7a65eb4a358bbb1a4a9dda8d47@stantz.qantel.com> Hi Fabio, The error is because a token created for the user is expired or expiring. Did you set a new UPS admin password like the docs suggested? The default may have expired. - Kelvin ---------------------------------------------------------------------------------------------------- From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Fabio Turizo Sent: Thursday, August 06, 2015 7:57 AM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] Aerogear Unified Push Server setup not working Well, still have issues with the admin application. I'm getting this Error 401: Unathorized errors in the admin interface. I work for a minute or two in the application and get the error, log out of the application/refresh browser and again after one or two minutes happens again. Quite annoying. Checking the server logs i see this exception: 2015-08-06 10:50:19,297 ERROR [org.keycloak.adapters.BearerTokenRequestAuthenticator] (default task-4) Failed to verify token: org.keycloak.VerificationException: Token is not active. ? ? ? ? at org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:43) [keycloak-core-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:16) [keycloak-core-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.adapters.BearerTokenRequestAuthenticator.authenticate(BearerTokenRequestAuthenticator.java:63) [keycloak-adapter-core-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:41) [keycloak-adapter-core-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.adapters.undertow.UndertowKeycloakAuthMech.keycloakAuthenticate(UndertowKeycloakAuthMech.java:82) [keycloak-undertow-adapter-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:61) [keycloak-undertow-adapter-1.0.5.Final.jar:] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) ? ? ? ? at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.0.5.Final.jar:] ? ? ? ? at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51] ? ? ? ? at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51] ? ? ? ? at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] 2015-08-06 10:51:51,799 ERROR [org.keycloak.adapters.BearerTokenRequestAuthenticator] (default task-14) Failed to verify token: org.keycloak.VerificationException: Token is not active. ? ? ? ? at org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:43) [keycloak-core-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:16) [keycloak-core-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.adapters.BearerTokenRequestAuthenticator.authenticate(BearerTokenRequestAuthenticator.java:63) [keycloak-adapter-core-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:41) [keycloak-adapter-core-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.adapters.undertow.UndertowKeycloakAuthMech.keycloakAuthenticate(UndertowKeycloakAuthMech.java:82) [keycloak-undertow-adapter-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:61) [keycloak-undertow-adapter-1.0.5.Final.jar:] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) ? ? ? ? at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.0.5.Final.jar:] ? ? ? ? at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51] ? ? ? ? at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51] ? ? ? ? at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] El jue., 6 de ago. de 2015 a la(s) 9:02 a. m., Fabio Turizo escribi?: Ok, i configured the HTTPS listener for the server and now the application works as intended. Many thanks! El mi?., 5 de ago. de 2015 a la(s) 5:13 p. m., Kelvin Lunsford escribi?: The error is because ssl is required. ? By default the https protocol scheme is required to access the UPS console when not using localhost as the URL host name. ? Https is not required for localhost access to the console.? You might see if you can tunnel into your AWS instance as localhost.? ? You will eventually need a cert and https connector configured in wildfly to access the restful interfaces.? ? - Kelvin ? ? From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Fabio Turizo Sent: Wednesday, August 05, 2015 7:30 AM To: aerogear-users at lists.jboss.org Subject: [Aerogear-users] Aerogear Unified Push Server setup not working ? Greetings. I've followed all instrucciones detailed in the AeroGear UPS Installation Guide but the server isn't working.? ? My setup is done in an AWS instance running with RHEL 7 installing Aerogear UPS v1.0.3 with a PostgreSQL 9.4 database (via AWS RDS) and using WildFly 8.2.1 Final with Oracle JDK 8 ? When i deploy the WARs (agpush and auth) everything is deployed fine. Trying to get in the admin ui gets me an Internal error. Checking the logs: ? 2015-08-05 10:11:08,832 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /ag-push/index.html: java.lang.RuntimeException: Can't resolve relative url from adapter config. ? ? ? ? at org.keycloak.adapters.AdapterDeploymentContext.getBaseBuilder(AdapterDeploymentContext.java:289) [keycloak-adapter-core-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:53) [keycloak-adapter-core-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:54) [keycloak-undertow-adapter-1.0.5.Final.jar:] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) ? ? ? ? at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.0.5.Final.jar:] ? ? ? ? at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.0.5.Final.jar:] ? ? ? ? at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) [undertow-core-1.1.8.Final.jar:1.1.8.Final] ? ? ? ? at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_51] ? ? ? ? at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_51] ? ? ? ? at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] ? Is there a configuration missing in the setup that causes this error? Any help is appreciated.? _______________________________________________ Aerogear-users mailing list Aerogear-users at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users From fabio.turizo at gmail.com Thu Aug 6 20:12:58 2015 From: fabio.turizo at gmail.com (Fabio Turizo) Date: Fri, 07 Aug 2015 00:12:58 +0000 Subject: [Aerogear-users] Aerogear Unified Push Server setup not working In-Reply-To: <5347cb7a65eb4a358bbb1a4a9dda8d47@stantz.qantel.com> References: <701caecae51a4c37845a119959c86b51@stantz.qantel.com> <5347cb7a65eb4a358bbb1a4a9dda8d47@stantz.qantel.com> Message-ID: Well, in the first login the application forced me to change the password so yes. I retried by restarting the server but still happens. El jue., 6 de ago. de 2015 a la(s) 3:24 p. m., Kelvin Lunsford < kelvin at qantel.com> escribi?: > Hi Fabio, > > The error is because a token created for the user is expired or expiring. > > Did you set a new UPS admin password like the docs suggested? The default > may have expired. > > - Kelvin > > > ---------------------------------------------------------------------------------------------------- > > From: aerogear-users-bounces at lists.jboss.org [mailto: > aerogear-users-bounces at lists.jboss.org] On Behalf Of Fabio Turizo > Sent: Thursday, August 06, 2015 7:57 AM > To: aerogear-users at lists.jboss.org > Subject: Re: [Aerogear-users] Aerogear Unified Push Server setup not > working > > Well, still have issues with the admin application. I'm getting this Error > 401: Unathorized errors in the admin interface. I work for a minute or two > in the application and get the error, log out of the application/refresh > browser and again after one or two minutes happens again. Quite annoying. > > Checking the server logs i see this exception: > > 2015-08-06 10:50:19,297 ERROR > [org.keycloak.adapters.BearerTokenRequestAuthenticator] (default task-4) > Failed to verify token: org.keycloak.VerificationException: Token > is not active. > at > org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:43) > [keycloak-core-1.0.5.Final.jar:] > at > org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:16) > [keycloak-core-1.0.5.Final.jar:] > at > org.keycloak.adapters.BearerTokenRequestAuthenticator.authenticate(BearerTokenRequestAuthenticator.java:63) > [keycloak-adapter-core-1.0.5.Final.jar:] > at > org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:41) > [keycloak-adapter-core-1.0.5.Final.jar:] > at > org.keycloak.adapters.undertow.UndertowKeycloakAuthMech.keycloakAuthenticate(UndertowKeycloakAuthMech.java:82) > [keycloak-undertow-adapter-1.0.5.Final.jar:] > at > org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:61) > [keycloak-undertow-adapter-1.0.5.Final.jar:] > at > io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) > [keycloak-undertow-adapter-1.0.5.Final.jar:] > at > org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) > [keycloak-undertow-adapter-1.0.5.Final.jar:] > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [rt.jar:1.8.0_51] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [rt.jar:1.8.0_51] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] > > 2015-08-06 10:51:51,799 ERROR > [org.keycloak.adapters.BearerTokenRequestAuthenticator] (default task-14) > Failed to verify token: org.keycloak.VerificationException: Token is not > active. > at > org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:43) > [keycloak-core-1.0.5.Final.jar:] > at > org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:16) > [keycloak-core-1.0.5.Final.jar:] > at > org.keycloak.adapters.BearerTokenRequestAuthenticator.authenticate(BearerTokenRequestAuthenticator.java:63) > [keycloak-adapter-core-1.0.5.Final.jar:] > at > org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:41) > [keycloak-adapter-core-1.0.5.Final.jar:] > at > org.keycloak.adapters.undertow.UndertowKeycloakAuthMech.keycloakAuthenticate(UndertowKeycloakAuthMech.java:82) > [keycloak-undertow-adapter-1.0.5.Final.jar:] > at > org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:61) > [keycloak-undertow-adapter-1.0.5.Final.jar:] > at > io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) > [keycloak-undertow-adapter-1.0.5.Final.jar:] > at > org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) > [keycloak-undertow-adapter-1.0.5.Final.jar:] > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [rt.jar:1.8.0_51] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [rt.jar:1.8.0_51] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] > > El jue., 6 de ago. de 2015 a la(s) 9:02 a. m., Fabio Turizo < > fabio.turizo at gmail.com> escribi?: > Ok, i configured the HTTPS listener for the server and now the application > works as intended. Many thanks! > > El mi?., 5 de ago. de 2015 a la(s) 5:13 p. m., Kelvin Lunsford < > kelvin at qantel.com> escribi?: > The error is because ssl is required. > > By default the https protocol scheme is required to access the UPS console > when not using localhost as the URL host name. > > Https is not required for localhost access to the console. You might see > if you can tunnel into your AWS instance as localhost. > > You will eventually need a cert and https connector configured in wildfly > to access the restful interfaces. > > - Kelvin > > > From: aerogear-users-bounces at lists.jboss.org [mailto: > aerogear-users-bounces at lists.jboss.org] On Behalf Of Fabio Turizo > Sent: Wednesday, August 05, 2015 7:30 AM > To: aerogear-users at lists.jboss.org > Subject: [Aerogear-users] Aerogear Unified Push Server setup not working > > Greetings. I've followed all instrucciones detailed in the AeroGear UPS > Installation Guide but the server isn't working. > > My setup is done in an AWS instance running with RHEL 7 installing > Aerogear UPS v1.0.3 with a PostgreSQL 9.4 database (via AWS RDS) and using > WildFly 8.2.1 Final with Oracle JDK 8 > > When i deploy the WARs (agpush and auth) everything is deployed fine. > Trying to get in the admin ui gets me an Internal error. Checking the logs: > > 2015-08-05 10:11:08,832 ERROR [io.undertow.request] (default task-1) > UT005023: Exception handling request to /ag-push/index.html: > java.lang.RuntimeException: Can't resolve relative url from adapter config. > at > org.keycloak.adapters.AdapterDeploymentContext.getBaseBuilder(AdapterDeploymentContext.java:289) > [keycloak-adapter-core-1.0.5.Final.jar:] > at > org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:53) > [keycloak-adapter-core-1.0.5.Final.jar:] > at > org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:54) > [keycloak-undertow-adapter-1.0.5.Final.jar:] > at > io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) > [keycloak-undertow-adapter-1.0.5.Final.jar:] > at > org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) > [keycloak-undertow-adapter-1.0.5.Final.jar:] > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) > [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) > [undertow-core-1.1.8.Final.jar:1.1.8.Final] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [rt.jar:1.8.0_51] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [rt.jar:1.8.0_51] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] > > Is there a configuration missing in the setup that causes this error? Any > help is appreciated. > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150807/ebb07c57/attachment-0001.html From scm.blanc at gmail.com Fri Aug 7 02:51:02 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 7 Aug 2015 08:51:02 +0200 Subject: [Aerogear-users] Aerogear Unified Push Server setup not working In-Reply-To: References: <701caecae51a4c37845a119959c86b51@stantz.qantel.com> <5347cb7a65eb4a358bbb1a4a9dda8d47@stantz.qantel.com> Message-ID: Hello Fabio, After you configured https did you clear the cache of your broswer before retrying ? If no, could you do that and see if it helps ? On Fri, Aug 7, 2015 at 2:12 AM, Fabio Turizo wrote: > Well, in the first login the application forced me to change the password > so yes. I retried by restarting the server but still happens. > > El jue., 6 de ago. de 2015 a la(s) 3:24 p. m., Kelvin Lunsford < > kelvin at qantel.com> escribi?: > >> Hi Fabio, >> >> The error is because a token created for the user is expired or expiring. >> >> Did you set a new UPS admin password like the docs suggested? The >> default may have expired. >> >> - Kelvin >> >> >> ---------------------------------------------------------------------------------------------------- >> >> From: aerogear-users-bounces at lists.jboss.org [mailto: >> aerogear-users-bounces at lists.jboss.org] On Behalf Of Fabio Turizo >> Sent: Thursday, August 06, 2015 7:57 AM >> To: aerogear-users at lists.jboss.org >> Subject: Re: [Aerogear-users] Aerogear Unified Push Server setup not >> working >> >> Well, still have issues with the admin application. I'm getting this >> Error 401: Unathorized errors in the admin interface. I work for a minute >> or two in the application and get the error, log out of the >> application/refresh browser and again after one or two minutes happens >> again. Quite annoying. >> >> Checking the server logs i see this exception: >> >> 2015-08-06 10:50:19,297 ERROR >> [org.keycloak.adapters.BearerTokenRequestAuthenticator] (default task-4) >> Failed to verify token: org.keycloak.VerificationException: Token >> is not active. >> at >> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:43) >> [keycloak-core-1.0.5.Final.jar:] >> at >> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:16) >> [keycloak-core-1.0.5.Final.jar:] >> at >> org.keycloak.adapters.BearerTokenRequestAuthenticator.authenticate(BearerTokenRequestAuthenticator.java:63) >> [keycloak-adapter-core-1.0.5.Final.jar:] >> at >> org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:41) >> [keycloak-adapter-core-1.0.5.Final.jar:] >> at >> org.keycloak.adapters.undertow.UndertowKeycloakAuthMech.keycloakAuthenticate(UndertowKeycloakAuthMech.java:82) >> [keycloak-undertow-adapter-1.0.5.Final.jar:] >> at >> org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:61) >> [keycloak-undertow-adapter-1.0.5.Final.jar:] >> at >> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >> [keycloak-undertow-adapter-1.0.5.Final.jar:] >> at >> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >> [keycloak-undertow-adapter-1.0.5.Final.jar:] >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >> [rt.jar:1.8.0_51] >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >> [rt.jar:1.8.0_51] >> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] >> >> 2015-08-06 10:51:51,799 ERROR >> [org.keycloak.adapters.BearerTokenRequestAuthenticator] (default task-14) >> Failed to verify token: org.keycloak.VerificationException: Token is not >> active. >> at >> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:43) >> [keycloak-core-1.0.5.Final.jar:] >> at >> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:16) >> [keycloak-core-1.0.5.Final.jar:] >> at >> org.keycloak.adapters.BearerTokenRequestAuthenticator.authenticate(BearerTokenRequestAuthenticator.java:63) >> [keycloak-adapter-core-1.0.5.Final.jar:] >> at >> org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:41) >> [keycloak-adapter-core-1.0.5.Final.jar:] >> at >> org.keycloak.adapters.undertow.UndertowKeycloakAuthMech.keycloakAuthenticate(UndertowKeycloakAuthMech.java:82) >> [keycloak-undertow-adapter-1.0.5.Final.jar:] >> at >> org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:61) >> [keycloak-undertow-adapter-1.0.5.Final.jar:] >> at >> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >> [keycloak-undertow-adapter-1.0.5.Final.jar:] >> at >> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >> [keycloak-undertow-adapter-1.0.5.Final.jar:] >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >> [rt.jar:1.8.0_51] >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >> [rt.jar:1.8.0_51] >> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] >> >> El jue., 6 de ago. de 2015 a la(s) 9:02 a. m., Fabio Turizo < >> fabio.turizo at gmail.com> escribi?: >> Ok, i configured the HTTPS listener for the server and now the >> application works as intended. Many thanks! >> >> El mi?., 5 de ago. de 2015 a la(s) 5:13 p. m., Kelvin Lunsford < >> kelvin at qantel.com> escribi?: >> The error is because ssl is required. >> >> By default the https protocol scheme is required to access the UPS >> console when not using localhost as the URL host name. >> >> Https is not required for localhost access to the console. You might see >> if you can tunnel into your AWS instance as localhost. >> >> You will eventually need a cert and https connector configured in wildfly >> to access the restful interfaces. >> >> - Kelvin >> >> >> From: aerogear-users-bounces at lists.jboss.org [mailto: >> aerogear-users-bounces at lists.jboss.org] On Behalf Of Fabio Turizo >> Sent: Wednesday, August 05, 2015 7:30 AM >> To: aerogear-users at lists.jboss.org >> Subject: [Aerogear-users] Aerogear Unified Push Server setup not working >> >> Greetings. I've followed all instrucciones detailed in the AeroGear UPS >> Installation Guide but the server isn't working. >> >> My setup is done in an AWS instance running with RHEL 7 installing >> Aerogear UPS v1.0.3 with a PostgreSQL 9.4 database (via AWS RDS) and using >> WildFly 8.2.1 Final with Oracle JDK 8 >> >> When i deploy the WARs (agpush and auth) everything is deployed fine. >> Trying to get in the admin ui gets me an Internal error. Checking the logs: >> >> 2015-08-05 10:11:08,832 ERROR [io.undertow.request] (default task-1) >> UT005023: Exception handling request to /ag-push/index.html: >> java.lang.RuntimeException: Can't resolve relative url from adapter config. >> at >> org.keycloak.adapters.AdapterDeploymentContext.getBaseBuilder(AdapterDeploymentContext.java:289) >> [keycloak-adapter-core-1.0.5.Final.jar:] >> at >> org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:53) >> [keycloak-adapter-core-1.0.5.Final.jar:] >> at >> org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:54) >> [keycloak-undertow-adapter-1.0.5.Final.jar:] >> at >> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >> [keycloak-undertow-adapter-1.0.5.Final.jar:] >> at >> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >> [keycloak-undertow-adapter-1.0.5.Final.jar:] >> at >> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) >> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) >> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >> [rt.jar:1.8.0_51] >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >> [rt.jar:1.8.0_51] >> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] >> >> Is there a configuration missing in the setup that causes this error? Any >> help is appreciated. >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150807/374984bf/attachment-0001.html From edewit at redhat.com Fri Aug 7 07:46:48 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Fri, 7 Aug 2015 13:46:48 +0200 Subject: [Aerogear-users] windows 10 Message-ID: Hi, After some tests we've released windows 10 support for aerogear-windows-push and aerogear-windows-oauth2 both have been published on nuget. With oauth2 that used to be only wnidows phone the upgrade to windows 10 make it possible to use it on tablet and desktop, just like push. Hope you like it -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150807/df83088f/attachment.html From lholmqui at redhat.com Mon Aug 10 09:30:08 2015 From: lholmqui at redhat.com (Luke Holmquist) Date: Mon, 10 Aug 2015 09:30:08 -0400 Subject: [Aerogear-users] Updated Node Sender released Message-ID: Now that the 1.1.0.Final release is about to be released of the UnifiedPush Server, i've released the 0.8.0 version of the Node Sender. This includes the new message format that the UPS needs. you can get it in all the normal ways -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150810/22c42895/attachment.html From fabio.turizo at gmail.com Mon Aug 10 10:06:07 2015 From: fabio.turizo at gmail.com (Fabio Turizo) Date: Mon, 10 Aug 2015 14:06:07 +0000 Subject: [Aerogear-users] Aerogear Unified Push Server setup not working In-Reply-To: References: <701caecae51a4c37845a119959c86b51@stantz.qantel.com> <5347cb7a65eb4a358bbb1a4a9dda8d47@stantz.qantel.com> Message-ID: Yes, cleared the browser cache and it still happens: [image: Captura_de_pantalla_081015_090246_AM.jpg] El vie., 7 de ago. de 2015 a la(s) 1:51 a. m., Sebastien Blanc < scm.blanc at gmail.com> escribi?: > Hello Fabio, > > After you configured https did you clear the cache of your broswer before > retrying ? If no, could you do that and see if it helps ? > > > On Fri, Aug 7, 2015 at 2:12 AM, Fabio Turizo > wrote: > >> Well, in the first login the application forced me to change the password >> so yes. I retried by restarting the server but still happens. >> >> El jue., 6 de ago. de 2015 a la(s) 3:24 p. m., Kelvin Lunsford < >> kelvin at qantel.com> escribi?: >> >>> Hi Fabio, >>> >>> The error is because a token created for the user is expired or expiring. >>> >>> Did you set a new UPS admin password like the docs suggested? The >>> default may have expired. >>> >>> - Kelvin >>> >>> >>> ---------------------------------------------------------------------------------------------------- >>> >>> From: aerogear-users-bounces at lists.jboss.org [mailto: >>> aerogear-users-bounces at lists.jboss.org] On Behalf Of Fabio Turizo >>> Sent: Thursday, August 06, 2015 7:57 AM >>> To: aerogear-users at lists.jboss.org >>> Subject: Re: [Aerogear-users] Aerogear Unified Push Server setup not >>> working >>> >>> Well, still have issues with the admin application. I'm getting this >>> Error 401: Unathorized errors in the admin interface. I work for a minute >>> or two in the application and get the error, log out of the >>> application/refresh browser and again after one or two minutes happens >>> again. Quite annoying. >>> >>> Checking the server logs i see this exception: >>> >>> 2015-08-06 10:50:19,297 ERROR >>> [org.keycloak.adapters.BearerTokenRequestAuthenticator] (default task-4) >>> Failed to verify token: org.keycloak.VerificationException: Token >>> is not active. >>> at >>> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:43) >>> [keycloak-core-1.0.5.Final.jar:] >>> at >>> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:16) >>> [keycloak-core-1.0.5.Final.jar:] >>> at >>> org.keycloak.adapters.BearerTokenRequestAuthenticator.authenticate(BearerTokenRequestAuthenticator.java:63) >>> [keycloak-adapter-core-1.0.5.Final.jar:] >>> at >>> org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:41) >>> [keycloak-adapter-core-1.0.5.Final.jar:] >>> at >>> org.keycloak.adapters.undertow.UndertowKeycloakAuthMech.keycloakAuthenticate(UndertowKeycloakAuthMech.java:82) >>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>> at >>> org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:61) >>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>> at >>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>> at >>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>> [rt.jar:1.8.0_51] >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>> [rt.jar:1.8.0_51] >>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] >>> >>> 2015-08-06 10:51:51,799 ERROR >>> [org.keycloak.adapters.BearerTokenRequestAuthenticator] (default task-14) >>> Failed to verify token: org.keycloak.VerificationException: Token is not >>> active. >>> at >>> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:43) >>> [keycloak-core-1.0.5.Final.jar:] >>> at >>> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:16) >>> [keycloak-core-1.0.5.Final.jar:] >>> at >>> org.keycloak.adapters.BearerTokenRequestAuthenticator.authenticate(BearerTokenRequestAuthenticator.java:63) >>> [keycloak-adapter-core-1.0.5.Final.jar:] >>> at >>> org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:41) >>> [keycloak-adapter-core-1.0.5.Final.jar:] >>> at >>> org.keycloak.adapters.undertow.UndertowKeycloakAuthMech.keycloakAuthenticate(UndertowKeycloakAuthMech.java:82) >>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>> at >>> org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:61) >>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>> at >>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>> at >>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>> [rt.jar:1.8.0_51] >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>> [rt.jar:1.8.0_51] >>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] >>> >>> El jue., 6 de ago. de 2015 a la(s) 9:02 a. m., Fabio Turizo < >>> fabio.turizo at gmail.com> escribi?: >>> Ok, i configured the HTTPS listener for the server and now the >>> application works as intended. Many thanks! >>> >>> El mi?., 5 de ago. de 2015 a la(s) 5:13 p. m., Kelvin Lunsford < >>> kelvin at qantel.com> escribi?: >>> The error is because ssl is required. >>> >>> By default the https protocol scheme is required to access the UPS >>> console when not using localhost as the URL host name. >>> >>> Https is not required for localhost access to the console. You might >>> see if you can tunnel into your AWS instance as localhost. >>> >>> You will eventually need a cert and https connector configured in >>> wildfly to access the restful interfaces. >>> >>> - Kelvin >>> >>> >>> From: aerogear-users-bounces at lists.jboss.org [mailto: >>> aerogear-users-bounces at lists.jboss.org] On Behalf Of Fabio Turizo >>> Sent: Wednesday, August 05, 2015 7:30 AM >>> To: aerogear-users at lists.jboss.org >>> Subject: [Aerogear-users] Aerogear Unified Push Server setup not working >>> >>> Greetings. I've followed all instrucciones detailed in the AeroGear UPS >>> Installation Guide but the server isn't working. >>> >>> My setup is done in an AWS instance running with RHEL 7 installing >>> Aerogear UPS v1.0.3 with a PostgreSQL 9.4 database (via AWS RDS) and using >>> WildFly 8.2.1 Final with Oracle JDK 8 >>> >>> When i deploy the WARs (agpush and auth) everything is deployed fine. >>> Trying to get in the admin ui gets me an Internal error. Checking the logs: >>> >>> 2015-08-05 10:11:08,832 ERROR [io.undertow.request] (default task-1) >>> UT005023: Exception handling request to /ag-push/index.html: >>> java.lang.RuntimeException: Can't resolve relative url from adapter config. >>> at >>> org.keycloak.adapters.AdapterDeploymentContext.getBaseBuilder(AdapterDeploymentContext.java:289) >>> [keycloak-adapter-core-1.0.5.Final.jar:] >>> at >>> org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:53) >>> [keycloak-adapter-core-1.0.5.Final.jar:] >>> at >>> org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:54) >>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>> at >>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>> at >>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>> at >>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) >>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) >>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>> [rt.jar:1.8.0_51] >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>> [rt.jar:1.8.0_51] >>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] >>> >>> Is there a configuration missing in the setup that causes this error? >>> Any help is appreciated. >>> _______________________________________________ >>> Aerogear-users mailing list >>> Aerogear-users at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >>> _______________________________________________ >>> Aerogear-users mailing list >>> Aerogear-users at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150810/fc1c8d0d/attachment-0001.html From scm.blanc at gmail.com Mon Aug 10 13:20:04 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Mon, 10 Aug 2015 19:20:04 +0200 Subject: [Aerogear-users] Aerogear Unified Push Server setup not working In-Reply-To: References: <701caecae51a4c37845a119959c86b51@stantz.qantel.com> <5347cb7a65eb4a358bbb1a4a9dda8d47@stantz.qantel.com> Message-ID: Hi Fabio, Sorry to hear you still have the issue. Could you try to reach out the keycloak user mailing list to expose your problem, they might have solutions ... In the mean time feel free to open a ticket on our project so that we can track this. On Mon, Aug 10, 2015 at 4:06 PM, Fabio Turizo wrote: > Yes, cleared the browser cache and it still happens: > > [image: Captura_de_pantalla_081015_090246_AM.jpg] > > El vie., 7 de ago. de 2015 a la(s) 1:51 a. m., Sebastien Blanc < > scm.blanc at gmail.com> escribi?: > >> Hello Fabio, >> >> After you configured https did you clear the cache of your broswer before >> retrying ? If no, could you do that and see if it helps ? >> >> >> On Fri, Aug 7, 2015 at 2:12 AM, Fabio Turizo >> wrote: >> >>> Well, in the first login the application forced me to change the >>> password so yes. I retried by restarting the server but still happens. >>> >>> El jue., 6 de ago. de 2015 a la(s) 3:24 p. m., Kelvin Lunsford < >>> kelvin at qantel.com> escribi?: >>> >>>> Hi Fabio, >>>> >>>> The error is because a token created for the user is expired or >>>> expiring. >>>> >>>> Did you set a new UPS admin password like the docs suggested? The >>>> default may have expired. >>>> >>>> - Kelvin >>>> >>>> >>>> ---------------------------------------------------------------------------------------------------- >>>> >>>> From: aerogear-users-bounces at lists.jboss.org [mailto: >>>> aerogear-users-bounces at lists.jboss.org] On Behalf Of Fabio Turizo >>>> Sent: Thursday, August 06, 2015 7:57 AM >>>> To: aerogear-users at lists.jboss.org >>>> Subject: Re: [Aerogear-users] Aerogear Unified Push Server setup not >>>> working >>>> >>>> Well, still have issues with the admin application. I'm getting this >>>> Error 401: Unathorized errors in the admin interface. I work for a minute >>>> or two in the application and get the error, log out of the >>>> application/refresh browser and again after one or two minutes happens >>>> again. Quite annoying. >>>> >>>> Checking the server logs i see this exception: >>>> >>>> 2015-08-06 10:50:19,297 ERROR >>>> [org.keycloak.adapters.BearerTokenRequestAuthenticator] (default task-4) >>>> Failed to verify token: org.keycloak.VerificationException: Token >>>> is not active. >>>> at >>>> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:43) >>>> [keycloak-core-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:16) >>>> [keycloak-core-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.adapters.BearerTokenRequestAuthenticator.authenticate(BearerTokenRequestAuthenticator.java:63) >>>> [keycloak-adapter-core-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:41) >>>> [keycloak-adapter-core-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.adapters.undertow.UndertowKeycloakAuthMech.keycloakAuthenticate(UndertowKeycloakAuthMech.java:82) >>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:61) >>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) >>>> at >>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>> at >>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>> [rt.jar:1.8.0_51] >>>> at >>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>> [rt.jar:1.8.0_51] >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] >>>> >>>> 2015-08-06 10:51:51,799 ERROR >>>> [org.keycloak.adapters.BearerTokenRequestAuthenticator] (default task-14) >>>> Failed to verify token: org.keycloak.VerificationException: Token is not >>>> active. >>>> at >>>> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:43) >>>> [keycloak-core-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:16) >>>> [keycloak-core-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.adapters.BearerTokenRequestAuthenticator.authenticate(BearerTokenRequestAuthenticator.java:63) >>>> [keycloak-adapter-core-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:41) >>>> [keycloak-adapter-core-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.adapters.undertow.UndertowKeycloakAuthMech.keycloakAuthenticate(UndertowKeycloakAuthMech.java:82) >>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:61) >>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) >>>> at >>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>> at >>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>> [rt.jar:1.8.0_51] >>>> at >>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>> [rt.jar:1.8.0_51] >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] >>>> >>>> El jue., 6 de ago. de 2015 a la(s) 9:02 a. m., Fabio Turizo < >>>> fabio.turizo at gmail.com> escribi?: >>>> Ok, i configured the HTTPS listener for the server and now the >>>> application works as intended. Many thanks! >>>> >>>> El mi?., 5 de ago. de 2015 a la(s) 5:13 p. m., Kelvin Lunsford < >>>> kelvin at qantel.com> escribi?: >>>> The error is because ssl is required. >>>> >>>> By default the https protocol scheme is required to access the UPS >>>> console when not using localhost as the URL host name. >>>> >>>> Https is not required for localhost access to the console. You might >>>> see if you can tunnel into your AWS instance as localhost. >>>> >>>> You will eventually need a cert and https connector configured in >>>> wildfly to access the restful interfaces. >>>> >>>> - Kelvin >>>> >>>> >>>> From: aerogear-users-bounces at lists.jboss.org [mailto: >>>> aerogear-users-bounces at lists.jboss.org] On Behalf Of Fabio Turizo >>>> Sent: Wednesday, August 05, 2015 7:30 AM >>>> To: aerogear-users at lists.jboss.org >>>> Subject: [Aerogear-users] Aerogear Unified Push Server setup not working >>>> >>>> Greetings. I've followed all instrucciones detailed in the AeroGear UPS >>>> Installation Guide but the server isn't working. >>>> >>>> My setup is done in an AWS instance running with RHEL 7 installing >>>> Aerogear UPS v1.0.3 with a PostgreSQL 9.4 database (via AWS RDS) and using >>>> WildFly 8.2.1 Final with Oracle JDK 8 >>>> >>>> When i deploy the WARs (agpush and auth) everything is deployed fine. >>>> Trying to get in the admin ui gets me an Internal error. Checking the logs: >>>> >>>> 2015-08-05 10:11:08,832 ERROR [io.undertow.request] (default task-1) >>>> UT005023: Exception handling request to /ag-push/index.html: >>>> java.lang.RuntimeException: Can't resolve relative url from adapter config. >>>> at >>>> org.keycloak.adapters.AdapterDeploymentContext.getBaseBuilder(AdapterDeploymentContext.java:289) >>>> [keycloak-adapter-core-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:53) >>>> [keycloak-adapter-core-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:54) >>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) >>>> at >>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>> at >>>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>> at >>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) >>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) >>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>> at >>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>> [rt.jar:1.8.0_51] >>>> at >>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>> [rt.jar:1.8.0_51] >>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] >>>> >>>> Is there a configuration missing in the setup that causes this error? >>>> Any help is appreciated. >>>> _______________________________________________ >>>> Aerogear-users mailing list >>>> Aerogear-users at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>> >>>> _______________________________________________ >>>> Aerogear-users mailing list >>>> Aerogear-users at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>> >>> >>> _______________________________________________ >>> Aerogear-users mailing list >>> Aerogear-users at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >>> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150810/23053e89/attachment-0001.html From fabio.turizo at gmail.com Mon Aug 10 17:24:16 2015 From: fabio.turizo at gmail.com (Fabio Turizo) Date: Mon, 10 Aug 2015 21:24:16 +0000 Subject: [Aerogear-users] Aerogear Unified Push Server setup not working In-Reply-To: References: <701caecae51a4c37845a119959c86b51@stantz.qantel.com> <5347cb7a65eb4a358bbb1a4a9dda8d47@stantz.qantel.com> Message-ID: Ok, i reported the situation in this issue: AGPUSH-1490 El lun., 10 de ago. de 2015 a la(s) 12:20 p. m., Sebastien Blanc < scm.blanc at gmail.com> escribi?: > Hi Fabio, > > Sorry to hear you still have the issue. Could you try to reach out the > keycloak user mailing list to expose your problem, they might have > solutions ... In the mean time feel free to open a ticket on our project so > that we can track this. > > > On Mon, Aug 10, 2015 at 4:06 PM, Fabio Turizo > wrote: > >> Yes, cleared the browser cache and it still happens: >> >> [image: Captura_de_pantalla_081015_090246_AM.jpg] >> >> El vie., 7 de ago. de 2015 a la(s) 1:51 a. m., Sebastien Blanc < >> scm.blanc at gmail.com> escribi?: >> >>> Hello Fabio, >>> >>> After you configured https did you clear the cache of your broswer >>> before retrying ? If no, could you do that and see if it helps ? >>> >>> >>> On Fri, Aug 7, 2015 at 2:12 AM, Fabio Turizo >>> wrote: >>> >>>> Well, in the first login the application forced me to change the >>>> password so yes. I retried by restarting the server but still happens. >>>> >>>> El jue., 6 de ago. de 2015 a la(s) 3:24 p. m., Kelvin Lunsford < >>>> kelvin at qantel.com> escribi?: >>>> >>>>> Hi Fabio, >>>>> >>>>> The error is because a token created for the user is expired or >>>>> expiring. >>>>> >>>>> Did you set a new UPS admin password like the docs suggested? The >>>>> default may have expired. >>>>> >>>>> - Kelvin >>>>> >>>>> >>>>> ---------------------------------------------------------------------------------------------------- >>>>> >>>>> From: aerogear-users-bounces at lists.jboss.org [mailto: >>>>> aerogear-users-bounces at lists.jboss.org] On Behalf Of Fabio Turizo >>>>> Sent: Thursday, August 06, 2015 7:57 AM >>>>> To: aerogear-users at lists.jboss.org >>>>> Subject: Re: [Aerogear-users] Aerogear Unified Push Server setup not >>>>> working >>>>> >>>>> Well, still have issues with the admin application. I'm getting this >>>>> Error 401: Unathorized errors in the admin interface. I work for a minute >>>>> or two in the application and get the error, log out of the >>>>> application/refresh browser and again after one or two minutes happens >>>>> again. Quite annoying. >>>>> >>>>> Checking the server logs i see this exception: >>>>> >>>>> 2015-08-06 10:50:19,297 ERROR >>>>> [org.keycloak.adapters.BearerTokenRequestAuthenticator] (default task-4) >>>>> Failed to verify token: org.keycloak.VerificationException: Token >>>>> is not active. >>>>> at >>>>> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:43) >>>>> [keycloak-core-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:16) >>>>> [keycloak-core-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.adapters.BearerTokenRequestAuthenticator.authenticate(BearerTokenRequestAuthenticator.java:63) >>>>> [keycloak-adapter-core-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:41) >>>>> [keycloak-adapter-core-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.adapters.undertow.UndertowKeycloakAuthMech.keycloakAuthenticate(UndertowKeycloakAuthMech.java:82) >>>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:61) >>>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) >>>>> at >>>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>>> at >>>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>>> [rt.jar:1.8.0_51] >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>>> [rt.jar:1.8.0_51] >>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] >>>>> >>>>> 2015-08-06 10:51:51,799 ERROR >>>>> [org.keycloak.adapters.BearerTokenRequestAuthenticator] (default task-14) >>>>> Failed to verify token: org.keycloak.VerificationException: Token is not >>>>> active. >>>>> at >>>>> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:43) >>>>> [keycloak-core-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.RSATokenVerifier.verifyToken(RSATokenVerifier.java:16) >>>>> [keycloak-core-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.adapters.BearerTokenRequestAuthenticator.authenticate(BearerTokenRequestAuthenticator.java:63) >>>>> [keycloak-adapter-core-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.adapters.RequestAuthenticator.authenticate(RequestAuthenticator.java:41) >>>>> [keycloak-adapter-core-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.adapters.undertow.UndertowKeycloakAuthMech.keycloakAuthenticate(UndertowKeycloakAuthMech.java:82) >>>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:61) >>>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) >>>>> at >>>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>>> at >>>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>>> [rt.jar:1.8.0_51] >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>>> [rt.jar:1.8.0_51] >>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] >>>>> >>>>> El jue., 6 de ago. de 2015 a la(s) 9:02 a. m., Fabio Turizo < >>>>> fabio.turizo at gmail.com> escribi?: >>>>> Ok, i configured the HTTPS listener for the server and now the >>>>> application works as intended. Many thanks! >>>>> >>>>> El mi?., 5 de ago. de 2015 a la(s) 5:13 p. m., Kelvin Lunsford < >>>>> kelvin at qantel.com> escribi?: >>>>> The error is because ssl is required. >>>>> >>>>> By default the https protocol scheme is required to access the UPS >>>>> console when not using localhost as the URL host name. >>>>> >>>>> Https is not required for localhost access to the console. You might >>>>> see if you can tunnel into your AWS instance as localhost. >>>>> >>>>> You will eventually need a cert and https connector configured in >>>>> wildfly to access the restful interfaces. >>>>> >>>>> - Kelvin >>>>> >>>>> >>>>> From: aerogear-users-bounces at lists.jboss.org [mailto: >>>>> aerogear-users-bounces at lists.jboss.org] On Behalf Of Fabio Turizo >>>>> Sent: Wednesday, August 05, 2015 7:30 AM >>>>> To: aerogear-users at lists.jboss.org >>>>> Subject: [Aerogear-users] Aerogear Unified Push Server setup not >>>>> working >>>>> >>>>> Greetings. I've followed all instrucciones detailed in the AeroGear >>>>> UPS Installation Guide but the server isn't working. >>>>> >>>>> My setup is done in an AWS instance running with RHEL 7 installing >>>>> Aerogear UPS v1.0.3 with a PostgreSQL 9.4 database (via AWS RDS) and using >>>>> WildFly 8.2.1 Final with Oracle JDK 8 >>>>> >>>>> When i deploy the WARs (agpush and auth) everything is deployed fine. >>>>> Trying to get in the admin ui gets me an Internal error. Checking the logs: >>>>> >>>>> 2015-08-05 10:11:08,832 ERROR [io.undertow.request] (default task-1) >>>>> UT005023: Exception handling request to /ag-push/index.html: >>>>> java.lang.RuntimeException: Can't resolve relative url from adapter config. >>>>> at >>>>> org.keycloak.adapters.AdapterDeploymentContext.getBaseBuilder(AdapterDeploymentContext.java:289) >>>>> [keycloak-adapter-core-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:53) >>>>> [keycloak-adapter-core-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.adapters.undertow.ServletKeycloakAuthMech.authenticate(ServletKeycloakAuthMech.java:54) >>>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:283) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.transition(SecurityContextImpl.java:300) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl$AuthAttempter.access$100(SecurityContextImpl.java:270) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl.attemptAuthentication(SecurityContextImpl.java:133) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl.authTransition(SecurityContextImpl.java:108) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.impl.SecurityContextImpl.authenticate(SecurityContextImpl.java:101) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) >>>>> at >>>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>>> at >>>>> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) >>>>> [keycloak-undertow-adapter-1.0.5.Final.jar:] >>>>> at >>>>> io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:261) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:248) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:77) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:167) >>>>> [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.server.Connectors.executeRootHandler(Connectors.java:199) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:761) >>>>> [undertow-core-1.1.8.Final.jar:1.1.8.Final] >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>>>> [rt.jar:1.8.0_51] >>>>> at >>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>>>> [rt.jar:1.8.0_51] >>>>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_51] >>>>> >>>>> Is there a configuration missing in the setup that causes this error? >>>>> Any help is appreciated. >>>>> _______________________________________________ >>>>> Aerogear-users mailing list >>>>> Aerogear-users at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>>> >>>>> _______________________________________________ >>>>> Aerogear-users mailing list >>>>> Aerogear-users at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>>> >>>> >>>> _______________________________________________ >>>> Aerogear-users mailing list >>>> Aerogear-users at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>> >>>> >>> _______________________________________________ >>> Aerogear-users mailing list >>> Aerogear-users at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150810/3cdf3362/attachment-0001.html From dpassos at redhat.com Mon Aug 10 20:04:53 2015 From: dpassos at redhat.com (Daniel Passos) Date: Mon, 10 Aug 2015 21:04:53 -0300 Subject: [Aerogear-users] What's new in AeroGear? Message-ID: Android - AeroGear Android Push 2.1.1 release - http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-AeroGear-Android-Push-2-2-1-td12026.html - GCM Topics support in Android and UPS is PR?d! - https://github.com/aerogear/aerogear-android-push/pull/50 - https://www.youtube.com/watch?v=s7tXcbua_sM - HttpStatus removed - https://github.com/aerogear/aerogear-android-authz/pull/34 - https://github.com/aerogear/aerogear-android-pipe/pull/40 - https://github.com/aerogear/aerogear-android-push/pull/48 - Change default Encrypted Store type from Passphrase to KeyStore - https://github.com/aerogear/aerogear-android-store/pull/34 Push - UnifiedPush Server 1.1.0.Final has been staged - http://lists.jboss.org/pipermail/aerogear-dev/2015-August/011947.html - UnifiedPush Java Sender 1.1.0.Final has been staged - http://lists.jboss.org/pipermail/aerogear-dev/2015-August/011948.html - GCM Topics support in Android and UPS is PR?d! - https://github.com/aerogear/aerogear-unifiedpush-server/pull/626 - https://www.youtube.com/watch?v=s7tXcbua_sM ? -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150810/6c3755df/attachment.html From kelvin at qantel.com Mon Aug 10 20:36:33 2015 From: kelvin at qantel.com (Kelvin Lunsford) Date: Tue, 11 Aug 2015 00:36:33 +0000 Subject: [Aerogear-users] categories have been hijacked Message-ID: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> Setting "categories" in the push payload was working for android and ios in cordova push plugin 1.1.1. For version 2.0.2 "categories" only works for ios. It looks like "categories" is being hijacked in android for a GCM feature called "topics". I liked "categories". I was using it. Now it's gone. GCM topics is not a drop-in replacement. It's not the same thing. New features should get new names and new commands. - Kelvin From supittma at redhat.com Mon Aug 10 21:11:35 2015 From: supittma at redhat.com (Summers Pittman) Date: Mon, 10 Aug 2015 21:11:35 -0400 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> Message-ID: On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford wrote: > Setting "categories" in the push payload was working for android and ios > in cordova push plugin 1.1.1. > > For version 2.0.2 "categories" only works for ios. > > It looks like "categories" is being hijacked in android for a GCM feature > called "topics". > > I liked "categories". I was using it. Now it's gone. GCM topics is not > a drop-in replacement. It's not the same thing. > What do categories do that topics do not do? > > New features should get new names and new commands. > > - Kelvin > > > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150810/9e0c8186/attachment.html From kelvin at qantel.com Tue Aug 11 00:43:39 2015 From: kelvin at qantel.com (Kelvin Lunsford) Date: Tue, 11 Aug 2015 04:43:39 +0000 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> Message-ID: <352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com> Hi Summers, GCM topic messages go to all devices registered for the topic. Topic notifications cannot be restricted to an alias or list of aliases. The way it worked before, and still works on ios, you can send a command to UPS with an "alias" name AND a "categories" name and it will only go to devices that have registered using that "alias" name AND that "categories" name. UPS finds which devices meet the selection criteria and push notification requests are sent for those devices. Requests with aliases and categories can target specific users in a group. With real "categories" you can segment users into groups, so every device can be assigned a category, and sub-groups can be defined by using more than one category per device. This is useful for geographic or organizational targeting. I have no problem with GCM topics. Just make it a new feature. Give me back my categories. - Kelvin --------------------------------------------------------------------------------------- From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Monday, August 10, 2015 6:12 PM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked > >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford wrote: >Setting "categories" in the push payload was working for android and ios in cordova push plugin 1.1.1. > >For version 2.0.2 "categories" only works for ios. > >It looks like "categories" is being hijacked in android for a GCM feature called "topics". > >I liked "categories".? I was using it.? Now it's gone.? GCM topics is not a drop-in replacement.? It's not the same thing. What do categories do that topics do not do?? >New features should get new names and new commands. > >- Kelvin From scm.blanc at gmail.com Tue Aug 11 02:35:11 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Tue, 11 Aug 2015 08:35:11 +0200 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> Message-ID: Hi, The version you have don't have yet GCM topics , this is still under development and is not released yet. You are facing a bug with 2.0.2 and cordova that has been reported https://issues.jboss.org/browse/AGCORDOVA-112 We are working on it. Sebi On Tue, Aug 11, 2015 at 2:36 AM, Kelvin Lunsford wrote: > Setting "categories" in the push payload was working for android and ios > in cordova push plugin 1.1.1. > > For version 2.0.2 "categories" only works for ios. > > It looks like "categories" is being hijacked in android for a GCM feature > called "topics". > > I liked "categories". I was using it. Now it's gone. GCM topics is not > a drop-in replacement. It's not the same thing. > > New features should get new names and new commands. > > - Kelvin > > > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150811/5c08addc/attachment.html From matzew at apache.org Tue Aug 11 07:06:20 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 11 Aug 2015 13:06:20 +0200 Subject: [Aerogear-users] [aerogear-dev] Updated Node Sender released In-Reply-To: References: Message-ID: yay! On Mon, Aug 10, 2015 at 3:30 PM, Luke Holmquist wrote: > Now that the 1.1.0.Final release is about to be released of the > UnifiedPush Server, i've released the 0.8.0 version of the Node Sender. > > This includes the new message format that the UPS needs. > > you can get it in all the normal ways > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150811/5da718c4/attachment-0001.html From matzew at apache.org Tue Aug 11 07:14:21 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 11 Aug 2015 13:14:21 +0200 Subject: [Aerogear-users] Fwd: [aerogear-dev] GCM Topic Messaging in UPS In-Reply-To: References: Message-ID: FYI ---------- Forwarded message ---------- From: Summers Pittman Date: Thu, Aug 6, 2015 at 3:42 PM Subject: [aerogear-dev] GCM Topic Messaging in UPS To: "List, AeroGear" Here's a video demo : https://www.youtube.com/watch?v=s7tXcbua_sM&feature=youtu.be Here's the PRs : * UPS : https://github.com/aerogear/aerogear-unifiedpush-server/pull/626 * AGDROID : https://github.com/aerogear/aerogear-android-push/pull/50 I would link the JIRAs but I closed those tabs ;) _______________________________________________ aerogear-dev mailing list aerogear-dev at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150811/50290cbc/attachment.html From matzew at apache.org Tue Aug 11 07:30:15 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 11 Aug 2015 13:30:15 +0200 Subject: [Aerogear-users] UPS push to IOS removes the badge In-Reply-To: References: <73b7e07608e140fc9ec4ecc7856d2f15@stantz.qantel.com> <431642b6ea1649739d46f85d7c24fe29@stantz.qantel.com> Message-ID: Hi Kelvin, I finally added the PR you suggested: https://github.com/aerogear/aerogear-unifiedpush-server/pull/629 -M On Fri, Jul 31, 2015 at 2:08 PM, Daniel Passos wrote: > On Thu, Jul 30, 2015 at 9:48 PM, Kelvin Lunsford > wrote: > >> Sorry Matt, >> >> Not ready to be a real contributor yet. Just a user. No git account. >> > > I understand your point here but I cannot agree with you. Notify about a > possible bug/whatever is a real contribution. > > Thank you for that. > > >> >> This looks like a 3 line change to me. Not big enough to learn everything >> required to do a PR. >> >> I might sign up later for a bigger change, but that's another topic. >> >> - Kelvin >> >> >> >> ------------------------------------------------------------------------------------ >> From: aerogear-users-bounces at lists.jboss.org [mailto: >> aerogear-users-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf >> Sent: Thursday, July 30, 2015 3:39 AM >> To: aerogear-users at lists.jboss.org >> Subject: Re: [Aerogear-users] UPS push to IOS removes the badge >> >> Hi Kevin, >> >> you mind sending a PR (pull request) to fix this bug? >> Sorry for it, its a pretty annoying issue for sure! >> >> -Matthias >> >> On Thursday, July 30, 2015, Kelvin Lunsford wrote: >> If UPS is given a push command with no "badge" value the IOS badge icon >> is being removed when the notification is received. Expected behavior is >> that the badge icon would be unchanged if no badge value is set. >> >> When USP receives a push command with no "badge" value it is sending APNS >> a "badge" value of -1. >> >> The Apple push payload spec says the badge icon is removed if the "badge" >> value is 0, and the icon is unchanged if there is no "badge" value. The >> spec does not say what happens if the "badge" value is less than zero. >> >> Tested devices are removing the badge icon when -1 is set. >> >> Please change UPS so no "badge" value is sent to APNS when the UPS >> command has no "badge" value. >> >> For example you could change the sendPushMessage function of >> APNsPushNotificationSender.java to: >> >> PayloadBuilder builder = APNS.newPayload() >> // adding recognized key values >> .alertBody(message.getAlert()) >> //.badge(message.getBadge()) // do not set badge here >> .sound(message.getSound()) >> .alertTitle(apns.getTitle()) >> .alertAction(apns.getAction()) >> .urlArgs(apns.getUrlArgs()) >> .category(apns.getActionCategory()) >> .localizedTitleKey(apns.getLocalizedTitleKey()); >> >> if (message.getBadge() >= 0) >> builder.badge(message.getBadge()); // only set badge if needed >> >> - Kelvin >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> >> -- >> Sent from Gmail Mobile >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> > > > > -- > -- Passos > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150811/13525771/attachment.html From supittma at redhat.com Tue Aug 11 08:31:25 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 11 Aug 2015 08:31:25 -0400 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: <352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com> References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> <352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com> Message-ID: On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford wrote: > Hi Summers, > > GCM topic messages go to all devices registered for the topic. Topic > notifications cannot be restricted to an alias or list of aliases. > > The way it worked before, and still works on ios, you can send a command > to UPS with an "alias" name AND a "categories" name and it will only go to > devices that have registered using that "alias" name AND that "categories" > name. UPS finds which devices meet the selection criteria and push > notification requests are sent for those devices. > > Requests with aliases and categories can target specific users in a group. > > With real "categories" you can segment users into groups, so every device > can be assigned a category, and sub-groups can be defined by using more > than one category per device. This is useful for geographic or > organizational targeting. > > I have no problem with GCM topics. Just make it a new feature. Give me > back my categories. > So the goal isn't to replace or hijack categories with topics. The goal is to leverage Google's API fully and transparently to the UPS user so that we make fewer calls and provide a better experience. You have some great use cases that haven't been brought up. Keep in mind that the PRs open right now are a "first draft" of the technology. Feel free to join in on the discussion about topics on aerogear-dev. It is really important we do this right and I think you can help with that. Summers > - Kelvin > > > > --------------------------------------------------------------------------------------- > From: aerogear-users-bounces at lists.jboss.org [mailto: > aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman > Sent: Monday, August 10, 2015 6:12 PM > To: aerogear-users at lists.jboss.org > Subject: Re: [Aerogear-users] categories have been hijacked > > > > > >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford > wrote: > >Setting "categories" in the push payload was working for android and ios > in cordova push plugin 1.1.1. > > > >For version 2.0.2 "categories" only works for ios. > > > >It looks like "categories" is being hijacked in android for a GCM feature > called "topics". > > > >I liked "categories". I was using it. Now it's gone. GCM topics is not > a drop-in replacement. It's not the same thing. > > What do categories do that topics do not do? > > >New features should get new names and new commands. > > > >- Kelvin > > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150811/f9ccc91e/attachment.html From edewit at redhat.com Tue Aug 11 10:17:16 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 11 Aug 2015 16:17:16 +0200 Subject: [Aerogear-users] Using Aerogear PushPlugin with Phonegap Build In-Reply-To: References: Message-ID: Hi Rodrigo, These dependencies are downloaded and installed with gradle when you run 'cordova build' There is no need to open it in Eclipse. If you want to change things and need and IDE I would advise you to use Android Studio. On Fri, Jul 24, 2015 at 4:14 PM, Rodrigo Del Canto wrote: > Hi Erik, > > Thanks for your reply. > > Actually I'm experiencing some issues, > > This is my configuration: > > 1. mac os x > > 2. $ cordova -v > > 5.1.1 > 3. cordova plugin add > https://github.com/aerogear/aerogear-pushplugin-cordova.git > > 4. I import to eclipse the android project to build it there. > > and I got these dependencies errors: > > - The import android.support cannot be resolved > > - The import org.jboss.aerogear.android cannot be resolved > > [image: Inline image 1] > > On Fri, Jul 24, 2015 at 3:13 AM, Erik Jan de Wit > wrote: > >> These instructions should work regardless of the platform: >> >> https://aerogear.org/docs/guides/aerogear-cordova/AerogearCordovaPush/ >> >> Or do you have some specific error? >> >> On Thu, Jul 23, 2015 at 7:12 PM, Rodrigo Del Canto >> wrote: >> >>> Hello, >>> >>> is there a place where I can follow instructions to make >>> aerogear-cordova-push to work with android ? >>> >>> On Fri, Jul 17, 2015 at 6:46 PM, Erik Jan de Wit >>> wrote: >>> >>>> the newer (2.x) version introduces some new functionality like metrics >>>> and is compatible with the newer UPS >>>> >>>> On Fri, Jul 17, 2015 at 4:16 PM, Fabio Turizo >>>> wrote: >>>> >>>>> Ok, tested it with that version and passed the build on all platforms. >>>>> A question, this version has the same funcionality as v2.0.2 and only >>>>> differs in the build system used for android? >>>>> >>>>> El vie., 17 de jul. de 2015 a la(s) 8:54 a. m., Erik Jan de Wit < >>>>> edewit at redhat.com> escribi?: >>>>> >>>>>> No, I mean the aerogear-cordova-push plugin there is also a 1.0.4 >>>>>> version that doesn't depend on gradle and will work with phonegap >>>>>> >>>>>> https://github.com/aerogear/aerogear-cordova-push/releases/tag/1.0.4 >>>>>> >>>>>> On Fri, Jul 17, 2015 at 3:24 PM, Fabio Turizo >>>>> > wrote: >>>>>> >>>>>>> When you refer that i could use version 1.0.4 of the plugin, are you >>>>>>> referring to the Promise Plugin? In that case do I have to specify this >>>>>>> dependency in the config.xml? >>>>>>> >>>>>>> >>>>>>> >>>>>>> El vie., 17 de jul. de 2015 a la(s) 3:43 a. m., Erik Jan de Wit < >>>>>>> edewit at redhat.com> escribi?: >>>>>>> >>>>>>>> That is because the new android library is using gradle and that is >>>>>>>> only supported in android platform 4. You could use version 1.0.4 of the >>>>>>>> plugin depending on what version of aerogear you are using. >>>>>>>> >>>>>>>> On Wed, Jul 15, 2015 at 4:31 PM, Fabio Turizo < >>>>>>>> fabio.turizo at gmail.com> wrote: >>>>>>>> >>>>>>>>> Greetings Eric. I was wondering if you were able to check this >>>>>>>>> issue and if there's an available solution >>>>>>>>> >>>>>>>>> El vie., 10 de jul. de 2015 a la(s) 9:12 a. m., Fabio Turizo < >>>>>>>>> fabio.turizo at gmail.com> escribi?: >>>>>>>>> >>>>>>>>>> Many thanks for your assistance! I tested it with version 2.0.2 >>>>>>>>>> and the build was succesful for iOS, but in android this error comes by: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *Error - Plugin error (you probably need to remove plugin files >>>>>>>>>> from your app): * >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *npm http GET >>>>>>>>>> https://registry.npmjs.org/aerogear-cordova-push/2.0.2 >>>>>>>>>> npm http 200 >>>>>>>>>> https://registry.npmjs.org/aerogear-cordova-push/2.0.2 >>>>>>>>>> npm http GET >>>>>>>>>> https://registry.npmjs.org/aerogear-cordova-push/-/aerogear-cordova-push-2.0.2.tgz >>>>>>>>>> >>>>>>>>>> npm http 200 >>>>>>>>>> https://registry.npmjs.org/aerogear-cordova-push/-/aerogear-cordova-push-2.0.2.tgz >>>>>>>>>> >>>>>>>>>> * >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *Failed to install >>>>>>>>>> 'org.jboss.aerogear.cordova.push':CordovaError: Plugin doesn't support this >>>>>>>>>> project's cordova-android version. cordova-android: 3.7.1, failed version >>>>>>>>>> requirement: >=4.0.0 at checkEngines >>>>>>>>>> (/home/ec2-user/.npm/lib/node_modules/plugman-npm/node_modules/cordova-lib/src/plugman/install.js:116:29) >>>>>>>>>> at >>>>>>>>>> /home/ec2-user/.npm/lib/node_modules/plugman-npm/node_modules/cordova-lib/src/plugman/install.js:289:16 >>>>>>>>>> at _fulfilled >>>>>>>>>> (/home/ec2-user/.npm/lib/node_modules/plugman-npm/node_modules/q/q.js:787:54) >>>>>>>>>> at self.promiseDispatch.done >>>>>>>>>> (/home/ec2-user/.npm/lib/node_modules/plugman-npm/node_modules/q/q.js:816:30) >>>>>>>>>> at Promise.promise.promiseDispatch >>>>>>>>>> (/home/ec2-user/.npm/lib/node_modules/plugman-npm/node_modules/q/q.js:749:13) >>>>>>>>>> at >>>>>>>>>> /home/ec2-user/.npm/lib/node_modules/plugman-npm/node_modules/q/q.js:557:44 >>>>>>>>>> at flush >>>>>>>>>> (/home/ec2-user/.npm/lib/node_modules/plugman-npm/node_modules/q/q.js:108:17) >>>>>>>>>> at process._tickCallback (node.js:442:13) Plugin doesn't support this >>>>>>>>>> project's cordova-android version. cordova-android: 3.7.1, failed version >>>>>>>>>> requirement: >=4.0.0* >>>>>>>>>> >>>>>>>>>> I'd greatly appreciate if you can fix this bug as well. >>>>>>>>>> Again, many thanks for your help. >>>>>>>>>> >>>>>>>>>> El vie., 10 de jul. de 2015 a la(s) 3:56 a. m., Erik Jan de Wit < >>>>>>>>>> edewit at redhat.com> escribi?: >>>>>>>>>> >>>>>>>>>>> Hi Fabio, >>>>>>>>>>> >>>>>>>>>>> I meant to say that you can upgrade your account to get 3rd >>>>>>>>>>> party plugins, but it seems that you already have that. What you have know >>>>>>>>>>> is an error in the dependency of the push plugin all the plugins are moving >>>>>>>>>>> to npm and changing there id to match npm. There is a mapping function, but >>>>>>>>>>> it seems that the promise plugin is not using that. This bug is fixed in >>>>>>>>>>> master I'm doing a release now version 2.0.2 will be available when you >>>>>>>>>>> read this mail >>>>>>>>>>> >>>>>>>>>>> On Thu, Jul 9, 2015 at 10:55 PM, Fabio Turizo < >>>>>>>>>>> fabio.turizo at gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Well, i'm not exactly sure if i could pay them to put the >>>>>>>>>>>> plugin in the platform. Looking at the site nothings comes up abput this. >>>>>>>>>>>> >>>>>>>>>>>> For the moment i tried reading their documentation and Phonegap >>>>>>>>>>>> Build supports 3rd party plugins by specifying the source of the plugin as >>>>>>>>>>>> npm in the config.xml declaration: >>>>>>>>>>>> >>>>>>>>>>>> *>>>>>>>>>>> version="2.0.1"/>* >>>>>>>>>>>> >>>>>>>>>>>> This works well as Phonegap Build detects this plugin when the >>>>>>>>>>>> application is uploaded, but the build fails for both iOS and Android with >>>>>>>>>>>> this error: >>>>>>>>>>>> >>>>>>>>>>>> Error - Plugin error (you probably need to remove plugin files >>>>>>>>>>>> from your app): npm http GET >>>>>>>>>>>> https://registry.npmjs.org/aerogear-cordova-push/2.0.1 npm >>>>>>>>>>>> http 200 https://registry.npmjs.org/aerogear-cordova-push/2.0.1 >>>>>>>>>>>> npm http GET >>>>>>>>>>>> https://registry.npmjs.org/aerogear-cordova-push/-/aerogear-cordova-push-2.0.1.tgz >>>>>>>>>>>> npm http 200 >>>>>>>>>>>> https://registry.npmjs.org/aerogear-cordova-push/-/aerogear-cordova-push-2.0.1.tgz >>>>>>>>>>>> Failed to install 'org.jboss.aerogear.cordova.push':Error: Expected plugin >>>>>>>>>>>> to have ID "com.vladstirbu.cordova.promise" but got "es6-promise-plugin". >>>>>>>>>>>> at checkID >>>>>>>>>>>> (/usr/local/lib/node_modules/plugman-npm/node_modules/cordova-lib/src/plugman/fetch.js:164:15) >>>>>>>>>>>> at >>>>>>>>>>>> /usr/local/lib/node_modules/plugman-npm/node_modules/cordova-lib/src/plugman/fetch.js:148:9 >>>>>>>>>>>> at _fulfilled >>>>>>>>>>>> (/usr/local/lib/node_modules/plugman-npm/node_modules/q/q.js:787:54) at >>>>>>>>>>>> self.promiseDispatch.done >>>>>>>>>>>> (/usr/local/lib/node_modules/plugman-npm/node_modules/q/q.js:816:30) at >>>>>>>>>>>> Promise.promise.promiseDispatch >>>>>>>>>>>> (/usr/local/lib/node_modules/plugman-npm/node_modules/q/q.js:749:13) at >>>>>>>>>>>> /usr/local/lib/node_modules/plugman-npm/node_modules/q/q.js:557:44 at flush >>>>>>>>>>>> (/usr/local/lib/node_modules/plugman-npm/node_modules/q/q.js:108:17) at >>>>>>>>>>>> process._tickCallback (node.js:419:13) Expected plugin to have ID >>>>>>>>>>>> "com.vladstirbu.cordova.promise" but got "es6-promise-plugin" >>>>>>>>>>>> >>>>>>>>>>>> By looking in the npm repositories effectively i see that there >>>>>>>>>>>> is a Promise plugin of ID *es6-promise-plugin *but it seems >>>>>>>>>>>> the dependency for the plugin is declared as *com.vladstirbu.cordova.promise >>>>>>>>>>>> *so the build fails. >>>>>>>>>>>> >>>>>>>>>>>> Any idea is this could be fixed and how? >>>>>>>>>>>> >>>>>>>>>>>> El jue., 9 de jul. de 2015 a la(s) 12:54 a. m., Erik Jan de Wit >>>>>>>>>>>> escribi?: >>>>>>>>>>>> >>>>>>>>>>>>> I've tried to get our plugin into Phonegap build, but it never >>>>>>>>>>>>> got accepted nor declined. But if you pay them I think you are able to use >>>>>>>>>>>>> any plugin you want. >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, Jul 9, 2015 at 1:35 AM, Fabio Turizo < >>>>>>>>>>>>> fabio.turizo at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I noticed that there's no equivalent for the aerogear cordova >>>>>>>>>>>>>> push plugin in the Phonegap Build plugin repository. Is there any way to >>>>>>>>>>>>>> use it with phonegap build? It'd be a waste if it's not possible. >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Aerogear-users mailing list >>>>>>>>>>>>>> Aerogear-users at lists.jboss.org >>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Cheers, >>>>>>>>>>>>> Erik Jan >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Aerogear-users mailing list >>>>>>>>>>>>> Aerogear-users at lists.jboss.org >>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Aerogear-users mailing list >>>>>>>>>>>> Aerogear-users at lists.jboss.org >>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Cheers, >>>>>>>>>>> Erik Jan >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Aerogear-users mailing list >>>>>>>>>>> Aerogear-users at lists.jboss.org >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Aerogear-users mailing list >>>>>>>>> Aerogear-users at lists.jboss.org >>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Cheers, >>>>>>>> Erik Jan >>>>>>>> _______________________________________________ >>>>>>>> Aerogear-users mailing list >>>>>>>> Aerogear-users at lists.jboss.org >>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Aerogear-users mailing list >>>>>>> Aerogear-users at lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Cheers, >>>>>> Erik Jan >>>>>> _______________________________________________ >>>>>> Aerogear-users mailing list >>>>>> Aerogear-users at lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Aerogear-users mailing list >>>>> Aerogear-users at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>>> >>>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> Erik Jan >>>> >>>> _______________________________________________ >>>> Aerogear-users mailing list >>>> Aerogear-users at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>>> >>>> >>> >>> _______________________________________________ >>> Aerogear-users mailing list >>> Aerogear-users at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >>> >> >> >> -- >> Cheers, >> Erik Jan >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150811/7bd9e19f/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 289009 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-users/attachments/20150811/7bd9e19f/attachment-0001.png From edewit at redhat.com Tue Aug 11 10:50:22 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Tue, 11 Aug 2015 16:50:22 +0200 Subject: [Aerogear-users] push.unregister() not working Cordova 5.0.0 for Android In-Reply-To: References: Message-ID: Hi, You would rarely need unregister this is from the android doc: You should rarely (if ever) need to call this method. Not only is it expensive in terms of resources, but it invalidates your registration ID, which should never change unnecessarily. A better approach is to simply have your server stop sending messages. Only use unregister if you want your application to stop using GCM permanently, or you have a compelling reason to recycle your registration ID The error you are getting is wrong though, seems that that it doesn't have a deviceId anymore I'll investigate On Tue, Jul 28, 2015 at 11:58 AM, Jes?s Mart?n Gonz?lez < jesus90martin at gmail.com> wrote: > Hi all, > > I'm starting to use pushplugin for Cordova android and i have followed all > instrucctions and examples available at: > https://aerogear.org/docs/specs/aerogear-cordova/Push.html and other > pages. I can receive notifications but when I try to unregister the device > an error message appear: "Seems this device is already unregistered" and it > is wrong because I am still receiving notifications. > > I am using cordova 5.0.0 and deploying to android, i am using this for > unregister: > > push.unregister(successHandler, errorHandler); > function successHandler() { > alert("notificaciones desactivadas"); > } > > function errorHandler(message) { > alert("error " + message); > } > > > Can you help me? > > Thanks > > -- > Jes?s Mart?n Gonzalez > Tel: +34 654420529 > > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150811/4c283d4b/attachment.html From supittma at redhat.com Tue Aug 11 10:59:32 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 11 Aug 2015 10:59:32 -0400 Subject: [Aerogear-users] push.unregister() not working Cordova 5.0.0 for Android In-Reply-To: References: Message-ID: Eric, Is this fixed by https://issues.jboss.org/browse/AGDROID-486? On Tue, Aug 11, 2015 at 10:50 AM, Erik Jan de Wit wrote: > Hi, > > You would rarely need unregister this is from the android doc: > > You should rarely (if ever) need to call this method. Not only is it > expensive in terms of resources, but it invalidates your registration ID, > which should never change unnecessarily. A better approach is to simply > have your server stop sending messages. Only use unregister if you want > your application to stop using GCM permanently, or you have a compelling > reason to recycle your registration ID > > The error you are getting is wrong though, seems that that it doesn't have > a deviceId anymore I'll investigate > > On Tue, Jul 28, 2015 at 11:58 AM, Jes?s Mart?n Gonz?lez < > jesus90martin at gmail.com> wrote: > >> Hi all, >> >> I'm starting to use pushplugin for Cordova android and i have followed >> all instrucctions and examples available at: >> https://aerogear.org/docs/specs/aerogear-cordova/Push.html and other >> pages. I can receive notifications but when I try to unregister the device >> an error message appear: "Seems this device is already unregistered" and it >> is wrong because I am still receiving notifications. >> >> I am using cordova 5.0.0 and deploying to android, i am using this for >> unregister: >> >> push.unregister(successHandler, errorHandler); >> function successHandler() { >> alert("notificaciones desactivadas"); >> } >> >> function errorHandler(message) { >> alert("error " + message); >> } >> >> >> Can you help me? >> >> Thanks >> >> -- >> Jes?s Mart?n Gonzalez >> Tel: +34 654420529 >> >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> > > > -- > Cheers, > Erik Jan > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150811/cc9b2c9b/attachment.html From supittma at redhat.com Tue Aug 11 13:03:18 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 11 Aug 2015 13:03:18 -0400 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> <352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com> Message-ID: Kelvin, For your tracking purposes : https://issues.jboss.org/browse/AGPUSH-1493 On Tue, Aug 11, 2015 at 8:31 AM, Summers Pittman wrote: > > > On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford > wrote: > >> Hi Summers, >> >> GCM topic messages go to all devices registered for the topic. Topic >> notifications cannot be restricted to an alias or list of aliases. >> >> The way it worked before, and still works on ios, you can send a command >> to UPS with an "alias" name AND a "categories" name and it will only go to >> devices that have registered using that "alias" name AND that "categories" >> name. UPS finds which devices meet the selection criteria and push >> notification requests are sent for those devices. >> >> Requests with aliases and categories can target specific users in a group. >> >> With real "categories" you can segment users into groups, so every device >> can be assigned a category, and sub-groups can be defined by using more >> than one category per device. This is useful for geographic or >> organizational targeting. >> >> I have no problem with GCM topics. Just make it a new feature. Give me >> back my categories. >> > > So the goal isn't to replace or hijack categories with topics. The goal is > to leverage Google's API fully and transparently to the UPS user so that we > make fewer calls and provide a better experience. You have some great use > cases that haven't been brought up. Keep in mind that the PRs open right > now are a "first draft" of the technology. Feel free to join in on the > discussion about topics on aerogear-dev. It is really important we do this > right and I think you can help with that. > > Summers > > >> - Kelvin >> >> >> >> --------------------------------------------------------------------------------------- >> From: aerogear-users-bounces at lists.jboss.org [mailto: >> aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman >> Sent: Monday, August 10, 2015 6:12 PM >> To: aerogear-users at lists.jboss.org >> Subject: Re: [Aerogear-users] categories have been hijacked >> >> >> > >> >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford >> wrote: >> >Setting "categories" in the push payload was working for android and ios >> in cordova push plugin 1.1.1. >> > >> >For version 2.0.2 "categories" only works for ios. >> > >> >It looks like "categories" is being hijacked in android for a GCM >> feature called "topics". >> > >> >I liked "categories". I was using it. Now it's gone. GCM topics is >> not a drop-in replacement. It's not the same thing. >> >> What do categories do that topics do not do? >> >> >New features should get new names and new commands. >> > >> >- Kelvin >> >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150811/f070b7ef/attachment.html From kelvin at qantel.com Tue Aug 11 20:13:32 2015 From: kelvin at qantel.com (Kelvin Lunsford) Date: Wed, 12 Aug 2015 00:13:32 +0000 Subject: [Aerogear-users] cordova plugin on android platform not working In-Reply-To: References: Message-ID: The new plugin version uses maven repositories for some dependent libraries. You need to add some local repositories in Eclipse. Go to the SDK Manager (Eclipse -> Window -> Android SDK Manager) and install Extras->Android Support Repository, and Extras->Google Repository. That will fix "android.support" and google play services problems. I'm not sure if it will fix your "org.jboss.aerogear.android" problem. In the new plugin version the aerogear libraries (android core, pipe, and push) are listed in a dependencies.gradle file. If the libraries do not get pulled at install or when the repositories are added you might try doing a CLI cordova build (or maybe just a prepare) to see if they get pulled. - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Rodrigo Del Canto Sent: Thursday, July 23, 2015 7:56 AM To: aerogear-users at lists.jboss.org Subject: [Aerogear-users] cordova plugin on android platform not working Hello guys, I trying to test the Aerogear push plugin for cordova with android but is not working. this is my configuration: 1. mac os x 2. $ cordova -v 5.1.1 3. cordova plugin add https://github.com/aerogear/aerogear-cordova-push.git 4. I'm importing the android project to eclipse to build it there. and I get this dependencies errors: - The import android.support cannot be resolved - The import org.jboss.aerogear.android cannot be resolved [Inline image 1] Any ideas? Thanks a lot! Rodrigo. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150812/6f278a68/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 87467 bytes Desc: image002.png Url : http://lists.jboss.org/pipermail/aerogear-users/attachments/20150812/6f278a68/attachment-0001.png From edewit at redhat.com Wed Aug 12 02:33:56 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 12 Aug 2015 08:33:56 +0200 Subject: [Aerogear-users] cordova plugin on android platform not working In-Reply-To: References: Message-ID: Hi You don't need to open the project with eclipse you can build and deploy with the cordova command line, if you want to use eclipse to open the project I suggest installing Thym (eclipse plugin for cordova) -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150812/0de95644/attachment.html From dpassos at redhat.com Tue Aug 11 13:39:45 2015 From: dpassos at redhat.com (Daniel Passos) Date: Tue, 11 Aug 2015 14:39:45 -0300 Subject: [Aerogear-users] cordova plugin on android platform not working In-Reply-To: References: Message-ID: Hey Rodrigo, Looking for you screenshot Cordova is creating the Android skeleton for Android Studio not for eclipse. (See gradle) On Thu, Jul 23, 2015 at 11:55 AM, Rodrigo Del Canto wrote: > Hello guys, > > I trying to test the Aerogear push plugin for cordova with android but is > not working. > > this is my configuration: > > 1. mac os x > > 2. $ cordova -v > > 5.1.1 > 3. cordova plugin add > https://github.com/aerogear/aerogear-cordova-push.git > > 4. I'm importing the android project to eclipse to build it there. > > and I get this dependencies errors: > > - The import android.support cannot be resolved > > - The import org.jboss.aerogear.android cannot be resolved > > [image: Inline image 1] > > > Any ideas? > > > Thanks a lot! > > Rodrigo. > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150811/f2f82c7c/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 289009 bytes Desc: not available Url : http://lists.jboss.org/pipermail/aerogear-users/attachments/20150811/f2f82c7c/attachment-0001.png From edewit at redhat.com Thu Aug 13 12:41:20 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Thu, 13 Aug 2015 18:41:20 +0200 Subject: [Aerogear-users] ng-cordova Message-ID: Hi, You might remember that we wanted to add the aerogear push plugin to the ng-cordova project. So we create the PR, half a year ago and now 3 PR's [1] later we have been added! Now getting started with cordova, angular and push is super easy. Keep an eye out for the next release. [1] https://github.com/driftyco/ng-cordova/pull/933 -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150813/4cd0d42e/attachment.html From scm.blanc at gmail.com Thu Aug 13 12:43:47 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Thu, 13 Aug 2015 18:43:47 +0200 Subject: [Aerogear-users] ng-cordova In-Reply-To: References: Message-ID: \o/ This is really cool On Thu, Aug 13, 2015 at 6:41 PM, Erik Jan de Wit wrote: > Hi, > > You might remember that we wanted to add the aerogear push plugin to the > ng-cordova project. So we create the PR, half a year ago and now 3 PR's [1] > later we have been added! Now getting started with cordova, angular and > push is super easy. Keep an eye out for the next release. > > [1] https://github.com/driftyco/ng-cordova/pull/933 > -- > Cheers, > Erik Jan > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150813/46dca26b/attachment.html From kelvin at qantel.com Thu Aug 13 23:44:18 2015 From: kelvin at qantel.com (Kelvin Lunsford) Date: Fri, 14 Aug 2015 03:44:18 +0000 Subject: [Aerogear-users] cordova push android BigText In-Reply-To: References: Message-ID: <61a93b83ff18470daaa6979bad21b908@stantz.qantel.com> On ios the message text wraps when a long message is displayed but on android only one line is displayed by default, truncating if too long. In a previous thread Erik pointed out that there is a lot of freedom for how messages are displayed in the Android notifications panel by making changes to NotificationMessageHandler.java. I coded up a change so I could test BigTextStyle in android. Using BigTextStyle on android lets the text wrap to multiple lines. With the change I can use a UPS request like: { "alias":["someuser"], "message":{ "alert":"a long message"", "badge":33, "gglbigtxt":"a long message", "gglsummry":"unread count", "gglinfo":"33" } } to display wrapping messages in both android and ios. Adding a summary line for the count value helps mitigate the missing badges on android. I added the "gglinfo" key to display any value in the info area. The "msgcnt" key displays in the info area but will not display a number less than 1. In NotificationMessageHandler.java before the line: manager.notify(appName, NOTIFICATION_ID, builder.build()); add: String tmp; if ((tmp = extras.getString("gglbigtxt")) != null) { NotificationCompat.BigTextStyle bigStyle = new NotificationCompat.BigTextStyle().bigText(tmp); if ((tmp = extras.getString("gglsummry")) != null) bigStyle.setSummaryText(tmp); if ((tmp = extras.getString("gglbigttl")) != null) bigStyle.setBigContentTitle(tmp); builder.setStyle(bigStyle); } if ((tmp = extras.getString("gglinfo")) != null) builder.setContentInfo(tmp); I'm not recommending this be added to the plugin project as is, but it might be worth looking at. - Kelvin From scm.blanc at gmail.com Fri Aug 14 01:54:53 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 14 Aug 2015 07:54:53 +0200 Subject: [Aerogear-users] cordova push android BigText In-Reply-To: <61a93b83ff18470daaa6979bad21b908@stantz.qantel.com> References: <61a93b83ff18470daaa6979bad21b908@stantz.qantel.com> Message-ID: Hi ! Thanks a lot for this tip and indeed I think it's worth a discussion to see if we could add some of these (android specific) keys to our sender API. Sebi On Fri, Aug 14, 2015 at 5:44 AM, Kelvin Lunsford wrote: > On ios the message text wraps when a long message is displayed but on > android only one line is displayed by default, truncating if too long. > > In a previous thread Erik pointed out that there is a lot of freedom for > how messages are displayed in the Android notifications panel by making > changes to NotificationMessageHandler.java. > > I coded up a change so I could test BigTextStyle in android. Using > BigTextStyle on android lets the text wrap to multiple lines. > > With the change I can use a UPS request like: > { > "alias":["someuser"], > "message":{ > "alert":"a long message"", > "badge":33, > "gglbigtxt":"a long message", > "gglsummry":"unread count", > "gglinfo":"33" > } > } > to display wrapping messages in both android and ios. Adding a summary > line for the count value helps mitigate the missing badges on android. > > I added the "gglinfo" key to display any value in the info area. The > "msgcnt" key displays in the info area but will not display a number less > than 1. > > In NotificationMessageHandler.java before the line: > > manager.notify(appName, NOTIFICATION_ID, builder.build()); > > add: > > String tmp; > if ((tmp = extras.getString("gglbigtxt")) != null) { > NotificationCompat.BigTextStyle bigStyle = new > NotificationCompat.BigTextStyle().bigText(tmp); > if ((tmp = extras.getString("gglsummry")) != null) > bigStyle.setSummaryText(tmp); > if ((tmp = extras.getString("gglbigttl")) != null) > bigStyle.setBigContentTitle(tmp); > builder.setStyle(bigStyle); > } > if ((tmp = extras.getString("gglinfo")) != null) > builder.setContentInfo(tmp); > > > I'm not recommending this be added to the plugin project as is, but it > might be worth looking at. > > - Kelvin > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150814/b17ab33f/attachment.html From matzew at apache.org Fri Aug 14 02:13:01 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Fri, 14 Aug 2015 08:13:01 +0200 Subject: [Aerogear-users] cordova push android BigText In-Reply-To: References: <61a93b83ff18470daaa6979bad21b908@stantz.qantel.com> Message-ID: I agree, would be for sure a nice option, even for the native Android lib? On Fri, Aug 14, 2015 at 7:54 AM, Sebastien Blanc wrote: > Hi ! > > Thanks a lot for this tip and indeed I think it's worth a discussion to > see if we could add some of these (android specific) keys to our sender > API. > > Sebi > > > On Fri, Aug 14, 2015 at 5:44 AM, Kelvin Lunsford > wrote: > >> On ios the message text wraps when a long message is displayed but on >> android only one line is displayed by default, truncating if too long. >> >> In a previous thread Erik pointed out that there is a lot of freedom for >> how messages are displayed in the Android notifications panel by making >> changes to NotificationMessageHandler.java. >> >> I coded up a change so I could test BigTextStyle in android. Using >> BigTextStyle on android lets the text wrap to multiple lines. >> >> With the change I can use a UPS request like: >> { >> "alias":["someuser"], >> "message":{ >> "alert":"a long message"", >> "badge":33, >> "gglbigtxt":"a long message", >> "gglsummry":"unread count", >> "gglinfo":"33" >> } >> } >> to display wrapping messages in both android and ios. Adding a summary >> line for the count value helps mitigate the missing badges on android. >> >> I added the "gglinfo" key to display any value in the info area. The >> "msgcnt" key displays in the info area but will not display a number less >> than 1. >> >> In NotificationMessageHandler.java before the line: >> >> manager.notify(appName, NOTIFICATION_ID, builder.build()); >> >> add: >> >> String tmp; >> if ((tmp = extras.getString("gglbigtxt")) != null) { >> NotificationCompat.BigTextStyle bigStyle = new >> NotificationCompat.BigTextStyle().bigText(tmp); >> if ((tmp = extras.getString("gglsummry")) != null) >> bigStyle.setSummaryText(tmp); >> if ((tmp = extras.getString("gglbigttl")) != null) >> bigStyle.setBigContentTitle(tmp); >> builder.setStyle(bigStyle); >> } >> if ((tmp = extras.getString("gglinfo")) != null) >> builder.setContentInfo(tmp); >> >> >> I'm not recommending this be added to the plugin project as is, but it >> might be worth looking at. >> >> - Kelvin >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> > > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150814/8b613e15/attachment-0001.html From scm.blanc at gmail.com Fri Aug 14 02:23:54 2015 From: scm.blanc at gmail.com (Sebastien Blanc) Date: Fri, 14 Aug 2015 08:23:54 +0200 Subject: [Aerogear-users] cordova push android BigText In-Reply-To: References: <61a93b83ff18470daaa6979bad21b908@stantz.qantel.com> Message-ID: Yes, that's why I directly mentioned the Sender API (so Native Lib is implicitly included ;) ) On Fri, Aug 14, 2015 at 8:13 AM, Matthias Wessendorf wrote: > I agree, would be for sure a nice option, even for the native Android lib? > > On Fri, Aug 14, 2015 at 7:54 AM, Sebastien Blanc > wrote: > >> Hi ! >> >> Thanks a lot for this tip and indeed I think it's worth a discussion to >> see if we could add some of these (android specific) keys to our sender >> API. >> >> Sebi >> >> >> On Fri, Aug 14, 2015 at 5:44 AM, Kelvin Lunsford >> wrote: >> >>> On ios the message text wraps when a long message is displayed but on >>> android only one line is displayed by default, truncating if too long. >>> >>> In a previous thread Erik pointed out that there is a lot of freedom for >>> how messages are displayed in the Android notifications panel by making >>> changes to NotificationMessageHandler.java. >>> >>> I coded up a change so I could test BigTextStyle in android. Using >>> BigTextStyle on android lets the text wrap to multiple lines. >>> >>> With the change I can use a UPS request like: >>> { >>> "alias":["someuser"], >>> "message":{ >>> "alert":"a long message"", >>> "badge":33, >>> "gglbigtxt":"a long message", >>> "gglsummry":"unread count", >>> "gglinfo":"33" >>> } >>> } >>> to display wrapping messages in both android and ios. Adding a summary >>> line for the count value helps mitigate the missing badges on android. >>> >>> I added the "gglinfo" key to display any value in the info area. The >>> "msgcnt" key displays in the info area but will not display a number less >>> than 1. >>> >>> In NotificationMessageHandler.java before the line: >>> >>> manager.notify(appName, NOTIFICATION_ID, builder.build()); >>> >>> add: >>> >>> String tmp; >>> if ((tmp = extras.getString("gglbigtxt")) != null) { >>> NotificationCompat.BigTextStyle bigStyle = new >>> NotificationCompat.BigTextStyle().bigText(tmp); >>> if ((tmp = extras.getString("gglsummry")) != null) >>> bigStyle.setSummaryText(tmp); >>> if ((tmp = extras.getString("gglbigttl")) != null) >>> bigStyle.setBigContentTitle(tmp); >>> builder.setStyle(bigStyle); >>> } >>> if ((tmp = extras.getString("gglinfo")) != null) >>> builder.setContentInfo(tmp); >>> >>> >>> I'm not recommending this be added to the plugin project as is, but it >>> might be worth looking at. >>> >>> - Kelvin >>> >>> _______________________________________________ >>> Aerogear-users mailing list >>> Aerogear-users at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >> >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150814/bac0f540/attachment.html From edewit at redhat.com Fri Aug 14 02:25:29 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Fri, 14 Aug 2015 08:25:29 +0200 Subject: [Aerogear-users] cordova push android BigText In-Reply-To: References: <61a93b83ff18470daaa6979bad21b908@stantz.qantel.com> Message-ID: With the Android lib you'll always need to create the Handler yourself, so we can't add it there. We already had an extra 'title' element that you could use instead of the app name, but yeah something like this might also be worth looking at. For windows we also have special messages that have a lot of formatting. On Fri, Aug 14, 2015 at 8:13 AM, Matthias Wessendorf wrote: > I agree, would be for sure a nice option, even for the native Android lib? > > On Fri, Aug 14, 2015 at 7:54 AM, Sebastien Blanc > wrote: > >> Hi ! >> >> Thanks a lot for this tip and indeed I think it's worth a discussion to >> see if we could add some of these (android specific) keys to our sender >> API. >> >> Sebi >> >> >> On Fri, Aug 14, 2015 at 5:44 AM, Kelvin Lunsford >> wrote: >> >>> On ios the message text wraps when a long message is displayed but on >>> android only one line is displayed by default, truncating if too long. >>> >>> In a previous thread Erik pointed out that there is a lot of freedom for >>> how messages are displayed in the Android notifications panel by making >>> changes to NotificationMessageHandler.java. >>> >>> I coded up a change so I could test BigTextStyle in android. Using >>> BigTextStyle on android lets the text wrap to multiple lines. >>> >>> With the change I can use a UPS request like: >>> { >>> "alias":["someuser"], >>> "message":{ >>> "alert":"a long message"", >>> "badge":33, >>> "gglbigtxt":"a long message", >>> "gglsummry":"unread count", >>> "gglinfo":"33" >>> } >>> } >>> to display wrapping messages in both android and ios. Adding a summary >>> line for the count value helps mitigate the missing badges on android. >>> >>> I added the "gglinfo" key to display any value in the info area. The >>> "msgcnt" key displays in the info area but will not display a number less >>> than 1. >>> >>> In NotificationMessageHandler.java before the line: >>> >>> manager.notify(appName, NOTIFICATION_ID, builder.build()); >>> >>> add: >>> >>> String tmp; >>> if ((tmp = extras.getString("gglbigtxt")) != null) { >>> NotificationCompat.BigTextStyle bigStyle = new >>> NotificationCompat.BigTextStyle().bigText(tmp); >>> if ((tmp = extras.getString("gglsummry")) != null) >>> bigStyle.setSummaryText(tmp); >>> if ((tmp = extras.getString("gglbigttl")) != null) >>> bigStyle.setBigContentTitle(tmp); >>> builder.setStyle(bigStyle); >>> } >>> if ((tmp = extras.getString("gglinfo")) != null) >>> builder.setContentInfo(tmp); >>> >>> >>> I'm not recommending this be added to the plugin project as is, but it >>> might be worth looking at. >>> >>> - Kelvin >>> >>> _______________________________________________ >>> Aerogear-users mailing list >>> Aerogear-users at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >> >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150814/447ef38d/attachment.html From kelvin at qantel.com Mon Aug 17 18:01:06 2015 From: kelvin at qantel.com (Kelvin Lunsford) Date: Mon, 17 Aug 2015 22:01:06 +0000 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> <352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com> Message-ID: Summers, What happens if a category name is not GCM topic compatible? - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Tuesday, August 11, 2015 10:03 AM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked Kelvin, For your tracking purposes : https://issues.jboss.org/browse/AGPUSH-1493 On Tue, Aug 11, 2015 at 8:31 AM, Summers Pittman > wrote: On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford > wrote: Hi Summers, GCM topic messages go to all devices registered for the topic. Topic notifications cannot be restricted to an alias or list of aliases. The way it worked before, and still works on ios, you can send a command to UPS with an "alias" name AND a "categories" name and it will only go to devices that have registered using that "alias" name AND that "categories" name. UPS finds which devices meet the selection criteria and push notification requests are sent for those devices. Requests with aliases and categories can target specific users in a group. With real "categories" you can segment users into groups, so every device can be assigned a category, and sub-groups can be defined by using more than one category per device. This is useful for geographic or organizational targeting. I have no problem with GCM topics. Just make it a new feature. Give me back my categories. So the goal isn't to replace or hijack categories with topics. The goal is to leverage Google's API fully and transparently to the UPS user so that we make fewer calls and provide a better experience. You have some great use cases that haven't been brought up. Keep in mind that the PRs open right now are a "first draft" of the technology. Feel free to join in on the discussion about topics on aerogear-dev. It is really important we do this right and I think you can help with that. Summers - Kelvin --------------------------------------------------------------------------------------- From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Monday, August 10, 2015 6:12 PM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked > >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford > wrote: >Setting "categories" in the push payload was working for android and ios in cordova push plugin 1.1.1. > >For version 2.0.2 "categories" only works for ios. > >It looks like "categories" is being hijacked in android for a GCM feature called "topics". > >I liked "categories". I was using it. Now it's gone. GCM topics is not a drop-in replacement. It's not the same thing. What do categories do that topics do not do? >New features should get new names and new commands. > >- Kelvin _______________________________________________ Aerogear-users mailing list Aerogear-users at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150817/04a9ebff/attachment-0001.html From supittma at redhat.com Tue Aug 18 09:25:56 2015 From: supittma at redhat.com (Summers Pittman) Date: Tue, 18 Aug 2015 09:25:56 -0400 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> <352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com> Message-ID: On Mon, Aug 17, 2015 at 6:01 PM, Kelvin Lunsford wrote: > Summers, > > > > What happens if a category name is not GCM topic compatible? > That is a good question. Currently you will get a error because it fails validation. We've created a JIRA to track this issue here : https://issues.jboss.org/browse/AGPUSH-1501 Keep the hits coming. > > > - Kelvin > > > > > > > > *From:* aerogear-users-bounces at lists.jboss.org [mailto: > aerogear-users-bounces at lists.jboss.org] *On Behalf Of *Summers Pittman > *Sent:* Tuesday, August 11, 2015 10:03 AM > > *To:* aerogear-users at lists.jboss.org > *Subject:* Re: [Aerogear-users] categories have been hijacked > > > > Kelvin, > > > > For your tracking purposes : https://issues.jboss.org/browse/AGPUSH-1493 > > > > On Tue, Aug 11, 2015 at 8:31 AM, Summers Pittman > wrote: > > > > > > On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford > wrote: > > Hi Summers, > > GCM topic messages go to all devices registered for the topic. Topic > notifications cannot be restricted to an alias or list of aliases. > > The way it worked before, and still works on ios, you can send a command > to UPS with an "alias" name AND a "categories" name and it will only go to > devices that have registered using that "alias" name AND that "categories" > name. UPS finds which devices meet the selection criteria and push > notification requests are sent for those devices. > > Requests with aliases and categories can target specific users in a group. > > With real "categories" you can segment users into groups, so every device > can be assigned a category, and sub-groups can be defined by using more > than one category per device. This is useful for geographic or > organizational targeting. > > I have no problem with GCM topics. Just make it a new feature. Give me > back my categories. > > > > So the goal isn't to replace or hijack categories with topics. The goal is > to leverage Google's API fully and transparently to the UPS user so that we > make fewer calls and provide a better experience. You have some great use > cases that haven't been brought up. Keep in mind that the PRs open right > now are a "first draft" of the technology. Feel free to join in on the > discussion about topics on aerogear-dev. It is really important we do this > right and I think you can help with that. > > > > Summers > > > > > - Kelvin > > > > --------------------------------------------------------------------------------------- > From: aerogear-users-bounces at lists.jboss.org [mailto: > aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman > Sent: Monday, August 10, 2015 6:12 PM > To: aerogear-users at lists.jboss.org > Subject: Re: [Aerogear-users] categories have been hijacked > > > > > > >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford > wrote: > >Setting "categories" in the push payload was working for android and ios > in cordova push plugin 1.1.1. > > > >For version 2.0.2 "categories" only works for ios. > > > >It looks like "categories" is being hijacked in android for a GCM feature > called "topics". > > > >I liked "categories". I was using it. Now it's gone. GCM topics is not > a drop-in replacement. It's not the same thing. > > What do categories do that topics do not do? > > >New features should get new names and new commands. > > > >- Kelvin > > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > > > > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150818/65fe12ea/attachment.html From kelvin at qantel.com Tue Aug 18 18:24:57 2015 From: kelvin at qantel.com (Kelvin Lunsford) Date: Tue, 18 Aug 2015 22:24:57 +0000 Subject: [Aerogear-users] categories have been hijacked In-Reply-To: References: <2024c7a2507b42e9b175e8dc81ca11fa@stantz.qantel.com> <352f01dee6a845b3ba73d29be8968e11@stantz.qantel.com> Message-ID: <708305c5f04c41cfa36ac5fbc2411030@stantz.qantel.com> You need topic compliant percent encoding/decoding functions to use on category names when setting them to/from topic names. You can encode by using the android.net.Uri.encode() function and replacing the characters missed by the encode() function. Uri.decode() will work as is. Equivalent encoding would have to be done in java for UPS when it accesses a topic. - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Tuesday, August 18, 2015 6:26 AM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked On Mon, Aug 17, 2015 at 6:01 PM, Kelvin Lunsford > wrote: Summers, What happens if a category name is not GCM topic compatible? That is a good question. Currently you will get a error because it fails validation. We've created a JIRA to track this issue here : https://issues.jboss.org/browse/AGPUSH-1501 Keep the hits coming. - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Tuesday, August 11, 2015 10:03 AM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked Kelvin, For your tracking purposes : https://issues.jboss.org/browse/AGPUSH-1493 On Tue, Aug 11, 2015 at 8:31 AM, Summers Pittman > wrote: On Tue, Aug 11, 2015 at 12:43 AM, Kelvin Lunsford > wrote: Hi Summers, GCM topic messages go to all devices registered for the topic. Topic notifications cannot be restricted to an alias or list of aliases. The way it worked before, and still works on ios, you can send a command to UPS with an "alias" name AND a "categories" name and it will only go to devices that have registered using that "alias" name AND that "categories" name. UPS finds which devices meet the selection criteria and push notification requests are sent for those devices. Requests with aliases and categories can target specific users in a group. With real "categories" you can segment users into groups, so every device can be assigned a category, and sub-groups can be defined by using more than one category per device. This is useful for geographic or organizational targeting. I have no problem with GCM topics. Just make it a new feature. Give me back my categories. So the goal isn't to replace or hijack categories with topics. The goal is to leverage Google's API fully and transparently to the UPS user so that we make fewer calls and provide a better experience. You have some great use cases that haven't been brought up. Keep in mind that the PRs open right now are a "first draft" of the technology. Feel free to join in on the discussion about topics on aerogear-dev. It is really important we do this right and I think you can help with that. Summers - Kelvin --------------------------------------------------------------------------------------- From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Summers Pittman Sent: Monday, August 10, 2015 6:12 PM To: aerogear-users at lists.jboss.org Subject: Re: [Aerogear-users] categories have been hijacked > >On Mon, Aug 10, 2015 at 8:36 PM, Kelvin Lunsford > wrote: >Setting "categories" in the push payload was working for android and ios in cordova push plugin 1.1.1. > >For version 2.0.2 "categories" only works for ios. > >It looks like "categories" is being hijacked in android for a GCM feature called "topics". > >I liked "categories". I was using it. Now it's gone. GCM topics is not a drop-in replacement. It's not the same thing. What do categories do that topics do not do? >New features should get new names and new commands. > >- Kelvin _______________________________________________ Aerogear-users mailing list Aerogear-users at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users _______________________________________________ Aerogear-users mailing list Aerogear-users at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150818/929d81f8/attachment-0001.html From matzew at apache.org Tue Aug 25 08:13:09 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Tue, 25 Aug 2015 14:13:09 +0200 Subject: [Aerogear-users] UPS 1.1.0-beta.4 and Openshift release (was: Re: Staging of UPS 1.1.0-beta.4 (was: Re: [aerogear-dev] Staging of UPS 1.1.0.Final)) Message-ID: Hello folks! On our way to 1.1.0.Final, we have released another beta release! This release contains changes to the DB schema and other small improvements. List of JIRAs https://issues.jboss.org/browse/AGPUSH/fixforversion/12327878 The release has been uploaded to Maven Central: http://search.maven.org/#search%7Cga%7C1%7Cunifiedpush It's, as usually, available on github too: https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.1.0-beta.4 Openshift update: As we move towards 1.1.0, the Openshift cartridge has been updated too, the new beta 4 is available on Openshift: https://github.com/aerogear/openshift-origin-cartridge-aerogear-push#installation Greetings, Matthias On Mon, Aug 17, 2015 at 8:28 PM, Matthias Wessendorf wrote: > Hello, > > since we had a few issues found and serious changes on the underlying DB > schema (see Karel's mail), here is the staging of another beta: > > > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6332/ > > > > Idea is to afterwards have a stable time of a week, and get the > 1.1.0.Final, finally out! > > Any comments? > > -Matthias > > > On Wed, Aug 12, 2015 at 8:52 AM, Sebastien Blanc > wrote: > >> Yes, I will discard the current staged release. >> Thanks Erik for reporting these issues. >> >> >> >> On Tue, Aug 11, 2015 at 10:39 PM, Matthias Wessendorf >> wrote: >> >>> I think this is aldo worth to be included to 1.1.0.Final >>> >>> >>> On Tuesday, August 11, 2015, Erik Jan de Wit wrote: >>> >>>> I found these issues: >>>> >>>> >>>> 1. AGPUSH-1492 Deleting >>>> an Application leaves installations >>>> 2. >>>> 1. >>>> 1. AGPUSH-1491 Android >>>> doesn't show installations >>>> >>>> >>>> On Tue, Aug 11, 2015 at 1:06 PM, Matthias Wessendorf >>> > wrote: >>>> >>>>> looking... >>>>> >>>>> On Fri, Aug 7, 2015 at 3:48 PM, Sebastien Blanc >>>>> wrote: >>>>> >>>>>> Hi team, >>>>>> >>>>>> I'm happy to announce that UPS 1.1.0 Final has been staged. >>>>>> >>>>>> Please test the staged release : >>>>>> >>>>>> >>>>>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6277 >>>>>> >>>>>> On Wednesday I'd like to press the button to release it to the wild. >>>>>> >>>>>> Sebi >>>>>> >>>>>> ps : the openshift update will follow >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> aerogear-dev mailing list >>>>>> aerogear-dev at 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 at lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>>> >>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> Erik Jan >>>> >>> >>> >>> -- >>> Sent from Gmail Mobile >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev at 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 > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150825/e299cd80/attachment.html From dpassos at redhat.com Tue Aug 25 08:26:15 2015 From: dpassos at redhat.com (Daniel Passos) Date: Tue, 25 Aug 2015 09:26:15 -0300 Subject: [Aerogear-users] AeroGear Android Push 2.2.2 Release Message-ID: Hey Guys, We found a bug in our AeroGear Android Push library. It was fixed and staged[1] What is new in this version? - AGDROID-492 - Categories field not working We?re planning to release it tomorrow (Wednesday) in the end of the day. Fell free to test it and let us know if you find any issues. [1] https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6402/ ? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150825/541096cc/attachment.html From matzew at apache.org Wed Aug 26 02:31:10 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 26 Aug 2015 08:31:10 +0200 Subject: [Aerogear-users] AeroGear Android Push 2.2.2 Release In-Reply-To: References: Message-ID: +1 On Tue, Aug 25, 2015 at 2:26 PM, Daniel Passos wrote: > Hey Guys, > > We found a bug in our AeroGear Android Push library. It was fixed and > staged[1] > > What is new in this version? > > - AGDROID-492 - > Categories field not working > > We?re planning to release it tomorrow (Wednesday) in the end of the day. > > Fell free to test it and let us know if you find any issues. > > [1] > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6402/ > ? > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150826/01cd9e18/attachment.html From edewit at redhat.com Wed Aug 26 02:55:27 2015 From: edewit at redhat.com (Erik Jan de Wit) Date: Wed, 26 Aug 2015 08:55:27 +0200 Subject: [Aerogear-users] AeroGear Android Push 2.2.2 Release In-Reply-To: References: Message-ID: Hot on the heels of the AeroGear Android Push library we also plan to update the cordova push plugin because we have the same issue AGCORDOVA-112 . After the release on Wednesday I'll update the plugin and stage that. On Tue, Aug 25, 2015 at 2:26 PM, Daniel Passos wrote: > Hey Guys, > > We found a bug in our AeroGear Android Push library. It was fixed and > staged[1] > > What is new in this version? > > - AGDROID-492 - > Categories field not working > > We?re planning to release it tomorrow (Wednesday) in the end of the day. > > Fell free to test it and let us know if you find any issues. > > [1] > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6402/ > ? > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Cheers, Erik Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150826/e5b8a270/attachment-0001.html From matzew at apache.org Wed Aug 26 03:48:05 2015 From: matzew at apache.org (Matthias Wessendorf) Date: Wed, 26 Aug 2015 09:48:05 +0200 Subject: [Aerogear-users] AeroGear Android Push 2.2.2 Release In-Reply-To: References: Message-ID: yay! On Wed, Aug 26, 2015 at 8:55 AM, Erik Jan de Wit wrote: > Hot on the heels of the AeroGear Android Push library we also plan to > update the cordova push plugin because we have the same issue > AGCORDOVA-112 . After the > release on Wednesday I'll update the plugin and stage that. > > On Tue, Aug 25, 2015 at 2:26 PM, Daniel Passos wrote: > >> Hey Guys, >> >> We found a bug in our AeroGear Android Push library. It was fixed and >> staged[1] >> >> What is new in this version? >> >> - AGDROID-492 - >> Categories field not working >> >> We?re planning to release it tomorrow (Wednesday) in the end of the day. >> >> Fell free to test it and let us know if you find any issues. >> >> [1] >> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6402/ >> ? >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> > > > -- > Cheers, > Erik Jan > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150826/cea3a4b7/attachment.html From dpassos at redhat.com Thu Aug 27 13:37:15 2015 From: dpassos at redhat.com (Daniel Passos) Date: Thu, 27 Aug 2015 14:37:15 -0300 Subject: [Aerogear-users] AeroGear Android Push 2.2.2 Release In-Reply-To: References: Message-ID: Just clicked on release button :) On Wed, Aug 26, 2015 at 4:48 AM, Matthias Wessendorf wrote: > yay! > > On Wed, Aug 26, 2015 at 8:55 AM, Erik Jan de Wit > wrote: > >> Hot on the heels of the AeroGear Android Push library we also plan to >> update the cordova push plugin because we have the same issue >> AGCORDOVA-112 . After the >> release on Wednesday I'll update the plugin and stage that. >> >> On Tue, Aug 25, 2015 at 2:26 PM, Daniel Passos >> wrote: >> >>> Hey Guys, >>> >>> We found a bug in our AeroGear Android Push library. It was fixed and >>> staged[1] >>> >>> What is new in this version? >>> >>> - AGDROID-492 - >>> Categories field not working >>> >>> We?re planning to release it tomorrow (Wednesday) in the end of the day. >>> >>> Fell free to test it and let us know if you find any issues. >>> >>> [1] >>> https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6402/ >>> ? >>> >>> _______________________________________________ >>> Aerogear-users mailing list >>> Aerogear-users at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >>> >> >> >> -- >> Cheers, >> Erik Jan >> >> _______________________________________________ >> Aerogear-users mailing list >> Aerogear-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-users >> >> > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150827/e9dcbec9/attachment.html From kelvin at qantel.com Thu Aug 27 16:26:40 2015 From: kelvin at qantel.com (Kelvin Lunsford) Date: Thu, 27 Aug 2015 20:26:40 +0000 Subject: [Aerogear-users] AeroGear Android Push 2.2.2 Release In-Reply-To: References: Message-ID: <55c1d497d9ab48558a4607d09b1ab8e7@stantz.qantel.com> I see the release on github: https://github.com/aerogear/aerogear-android-push/releases/tag/2.2.2 Why does the page say there are 48 commits to master since this tag? - Kelvin From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Daniel Passos Sent: Thursday, August 27, 2015 10:37 AM To: aerogear-users at lists.jboss.org Cc: AeroGear Developer Mailing List Subject: Re: [Aerogear-users] AeroGear Android Push 2.2.2 Release Just clicked on release button :) On Wed, Aug 26, 2015 at 4:48 AM, Matthias Wessendorf > wrote: yay! On Wed, Aug 26, 2015 at 8:55 AM, Erik Jan de Wit > wrote: Hot on the heels of the AeroGear Android Push library we also plan to update the cordova push plugin because we have the same issue AGCORDOVA-112. After the release on Wednesday I'll update the plugin and stage that. On Tue, Aug 25, 2015 at 2:26 PM, Daniel Passos > wrote: Hey Guys, We found a bug in our AeroGear Android Push library. It was fixed and staged[1] What is new in this version? AGDROID-492 - Categories field not working We?re planning to release it tomorrow (Wednesday) in the end of the day. Fell free to test it and let us know if you find any issues. [1] https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6402/ ? _______________________________________________ Aerogear-users mailing list Aerogear-users at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users -- Cheers, Erik Jan _______________________________________________ Aerogear-users mailing list Aerogear-users at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ Aerogear-users mailing list Aerogear-users at lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-users -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150827/42a476bf/attachment-0001.html From dpassos at redhat.com Thu Aug 27 16:57:17 2015 From: dpassos at redhat.com (Daniel Passos) Date: Thu, 27 Aug 2015 17:57:17 -0300 Subject: [Aerogear-users] AeroGear Android Push 2.2.2 Release In-Reply-To: <55c1d497d9ab48558a4607d09b1ab8e7@stantz.qantel.com> References: <55c1d497d9ab48558a4607d09b1ab8e7@stantz.qantel.com> Message-ID: Pretty much because we follow different workflow for each branch. On Thu, Aug 27, 2015 at 5:26 PM, Kelvin Lunsford wrote: > I see the release on github: > https://github.com/aerogear/aerogear-android-push/releases/tag/2.2.2 > > > > Why does the page say there are 48 commits to master since this tag? > > > > - Kelvin > > > > *From:* aerogear-users-bounces at lists.jboss.org [mailto: > aerogear-users-bounces at lists.jboss.org] *On Behalf Of *Daniel Passos > *Sent:* Thursday, August 27, 2015 10:37 AM > *To:* aerogear-users at lists.jboss.org > *Cc:* AeroGear Developer Mailing List > *Subject:* Re: [Aerogear-users] AeroGear Android Push 2.2.2 Release > > > > Just clicked on release button :) > > > > On Wed, Aug 26, 2015 at 4:48 AM, Matthias Wessendorf > wrote: > > yay! > > > > On Wed, Aug 26, 2015 at 8:55 AM, Erik Jan de Wit > wrote: > > Hot on the heels of the AeroGear Android Push library we also plan to > update the cordova push plugin because we have the same issue > AGCORDOVA-112 . After the > release on Wednesday I'll update the plugin and stage that. > > > > On Tue, Aug 25, 2015 at 2:26 PM, Daniel Passos wrote: > > Hey Guys, > > We found a bug in our AeroGear Android Push library. It was fixed and > staged[1] > > What is new in this version? > > AGDROID-492 - Categories > field not working > > We?re planning to release it tomorrow (Wednesday) in the end of the day. > > Fell free to test it and let us know if you find any issues. > > [1] > https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-6402/ > > ? > > > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > > > > > -- > > Cheers, > > Erik Jan > > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > > > > > -- > > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > > > > -- > > -- Passos > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > > -- -- Passos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150827/f7bce5e8/attachment.html From nifs.arpegiuz at gmail.com Fri Aug 28 10:32:47 2015 From: nifs.arpegiuz at gmail.com (Naif) Date: Fri, 28 Aug 2015 07:32:47 -0700 (MST) Subject: [Aerogear-users] Android Native Login to Keycloak Message-ID: <1440772367594-219.post@n5.nabble.com> !!Hello everyone!! I was looking for some example/insight around an android native login to Keycloak, because, i would not like to use the typical browser login method(i.e using a WebView): https://aerogear.org/docs/guides/security/img/keycloak-1.jpg Until now, i have thought about coding a REST Web Service to receive user login, extending Keycloak API; but, i do not know the correct approach in this case. Any help would be appreciated, thanks in advance. -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Android-Native-Login-to-Keycloak-tp219.html Sent from the aerogear-users mailing list archive at Nabble.com. From supittma at redhat.com Fri Aug 28 11:35:03 2015 From: supittma at redhat.com (Summers Pittman) Date: Fri, 28 Aug 2015 11:35:03 -0400 Subject: [Aerogear-users] Android Native Login to Keycloak In-Reply-To: <1440772367594-219.post@n5.nabble.com> References: <1440772367594-219.post@n5.nabble.com> Message-ID: It may be suffering from a bit of bitrot, but here is a example using Android's Authentication framework to do a native integration with KC. https://github.com/aerogear/aerogear-android-cookbook/tree/keycloak-authenticator/KeyCloakAuthenticator On Fri, Aug 28, 2015 at 10:32 AM, Naif wrote: > !!Hello everyone!! > > I was looking for some example/insight around an android native login to > Keycloak, because, i would not like to use the typical browser login > method(i.e using a WebView): > > https://aerogear.org/docs/guides/security/img/keycloak-1.jpg > > Until now, i have thought about coding a REST Web Service to receive user > login, extending Keycloak API; but, i do not know the correct approach in > this case. > > Any help would be appreciated, thanks in advance. > > > > > > > > > -- > View this message in context: > http://aerogear-users.1116366.n5.nabble.com/Android-Native-Login-to-Keycloak-tp219.html > Sent from the aerogear-users mailing list archive at Nabble.com. > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150828/814d0d53/attachment.html From nifs.arpegiuz at gmail.com Fri Aug 28 19:42:43 2015 From: nifs.arpegiuz at gmail.com (Naif) Date: Fri, 28 Aug 2015 16:42:43 -0700 (MST) Subject: [Aerogear-users] Android Native Login to Keycloak In-Reply-To: References: <1440772367594-219.post@n5.nabble.com> Message-ID: <1440805363803-221.post@n5.nabble.com> Thanks for the reply I downloaded the android project, and i have followed the instructions; I imported 'demo-realm.json' and create the 'keycloak.json' file(added on res/raw), but, when i run the project, i get on my smartphone: /WE'RE SORRY ... Invalid parameter: redirect_uri/ on the server console, i get: /WARN [org.keycloak.events] (default task-50) type=LOGIN_ERROR, realmId=98ac4271-17a4-490a-97b3-d4f11d05510b, clientId=Android, userId=null, ipAddress=192.168.0.16, error=invalid_redirect_uri, response_type=code, redirect_uri=urn:ietf:wg:oauth:2.0:oob/ and in my keycloak admin console(Clients -> Android -> Settings): /Access Type: confidential Valid Redirect URIs: http://oauth2callback Web Origins: http://oauth2callback/ Do you know, how can i solve this? -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Android-Native-Login-to-Keycloak-tp219p221.html Sent from the aerogear-users mailing list archive at Nabble.com. From supittma at redhat.com Mon Aug 31 10:51:56 2015 From: supittma at redhat.com (Summers Pittman) Date: Mon, 31 Aug 2015 10:51:56 -0400 Subject: [Aerogear-users] Android Native Login to Keycloak In-Reply-To: <1440805363803-221.post@n5.nabble.com> References: <1440772367594-219.post@n5.nabble.com> <1440805363803-221.post@n5.nabble.com> Message-ID: On Fri, Aug 28, 2015 at 7:42 PM, Naif wrote: > Thanks for the reply > > I downloaded the android project, and i have followed the instructions; I > imported 'demo-realm.json' and create the 'keycloak.json' file(added on > res/raw), but, when i run the project, i get on my smartphone: > > /WE'RE SORRY ... > Invalid parameter: redirect_uri/ > > on the server console, i get: > > /WARN [org.keycloak.events] (default task-50) type=LOGIN_ERROR, > realmId=98ac4271-17a4-490a-97b3-d4f11d05510b, clientId=Android, > userId=null, > ipAddress=192.168.0.16, error=invalid_redirect_uri, response_type=code, > redirect_uri=urn:ietf:wg:oauth:2.0:oob/ > ^^^ Redirect uri your client is sending > > and in my keycloak admin console(Clients -> Android -> Settings): > > /Access Type: confidential > Valid Redirect URIs: http://oauth2callback ^^^ Redirect URI your server is expecting > > Web Origins: http://oauth2callback/ > > Do you know, how can i solve this? > Change one to the other. I would suggest setting your redirect uri in the KC console to urn:ietf:wg:oauth:2.0:oob/ > > > > -- > View this message in context: > http://aerogear-users.1116366.n5.nabble.com/Android-Native-Login-to-Keycloak-tp219p221.html > Sent from the aerogear-users mailing list archive at Nabble.com. > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20150831/e01e540c/attachment-0001.html