May 2016 - Aerogear-users - Jboss List Archives

by Walto, David

Hi, I a new AeroGear unified push notification user. I am trying to create a simple push notification from a WebSphere java application. I have created a couple of push notification classes to test (below) and both version I get the error: SenderClient E Send did not succeed: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 64 I have the following jars for this application. [cid:image001.png@01D0EB25.5E1F6EE0] [cid:image003.png@01D0EB25.C89EC4F0] Any direction how to resolve this would be greatly appreciated. Thanks in advance. David Walto Senior Application Engineer | EMR Engineering and Integration Baystate Health | Information & Technology 1550 Main Street, Springfield, MA 01199 | p: 413-794-0627 | f: 413-794-5570 ---------------------------------------------------------------------- Please view our annual report at http://baystatehealth.org/annualreport CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please reply to the sender immediately or by telephone at 413-794-0000 and destroy all copies of this communication and any attachments. For further information regarding Baystate Health's privacy policy, please visit our Internet site at http://baystatehealth.org.

8 years, 1 month

4
5
0 / 0

Unified push server development environment setup

by mo

Hi, I'm trying to run the unified push server in a development environment to troubleshoot and understand it better. I'm wondering if there is any documentation available to assist me with setting up development environment for it. I've looked though documents under "Contributing to AeroGear", but I am in need of a more detailed guide. I'd like to get to a point where I can run unified push, break point, and inspect variables, and so on. So far I've managed to run 'mvn test' successfully on the unified push server source code. I use Eclipse, so I wanted to import the project. I get quite a lot of errors in doing so. I am troubleshooting version 1.0.2. We use OpenShift to deploy the aerogear server. I appreciate any help. Thank you. Michi Oshima -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Unified-push-server-developme... Sent from the aerogear-users mailing list archive at Nabble.com.

9 years

4
6
0 / 0

categories have been hijacked

by Kelvin Lunsford

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

9 years

5
18
0 / 0

UnifiedPush Node sender move to Promises

by Luke Holmquist

Hello people, I think i would like to move the unifiedpush-node-sender, https://github.com/aerogear/aerogear-unifiedpush-nodejs-client , to be Promise based. Currently it uses callback pattern that many node.js packages use as well as emitting events. When i first created this 3 years ago, that was sort of the standard way of doing things, but Promises have become very popular(i know i love them :)) and have been a native feature since node 0.12.x considering we have not yet hit a 1.0.0, we can pretty much just make this change and we will be ok. If this is to big of a change all at once, we could always do both callbacks and Promises. I think we did this for Datamanager in the past. Perhaps once we fully move to promises, then we can hit a 1.0.0 My only concern is other projects that might be using the sender that are not yet on node 0.12 or above, since this is when promises became native. I would really like to not have to include the polyfill. i suppose those users would need to stick to the previous versions then. anyway, would like to hear some thoughts. -Luke

9 years, 4 months

2
4
0 / 0

Device registration - Method not allowed

by Philipp Koetz, mVISE AG

Hello, we have encountered a problem while registering Android devices against the unified push server. Apple devices are not affected and can register successfull. We are using org.jboss.aerogear:aerogear-android-push:2.2.1 as client lib. Could you also provide a Deeplink which we can manually test the device registration? 2016-05-25 13:20:15,193 WARN [org.jboss.resteasy.core.ExceptionHandler] (default task-29) failed to execute: javax.ws.rs.NotAllowedException: No resource method found for GET, return 405 with Allow header at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:375) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:114) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.core.registry.RootNode.match(RootNode.java:43) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:48) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:444) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:234) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:171) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.10.Final.jar:] at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.10.Final.jar:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final] at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:86) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at org.jboss.aerogear.unifiedpush.rest.util.VersionFilter.doFilter(VersionFilter.java:65) [unifiedpush-jaxrs-1.1.3.Final.jar:1.1.3.Final] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:60) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at org.jboss.aerogear.unifiedpush.service.filter.HttpContextFilter.doFilter(HttpContextFilter.java:55) [unifiedpush-service-1.1.3.Final.jar:1.1.3.Final] at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:60) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) 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.UndertowAuthenticatedActionsHandler.handleRequest(UndertowAuthenticatedActionsHandler.java:66) [keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final] at org.keycloak.adapters.undertow.UndertowAuthenticatedActionsHandler.handleRequest(UndertowAuthenticatedActionsHandler.java:66) [keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.Final] at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) [undertow-servlet-1.1.8.Final.jar:1.1.8.Final] at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) [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.3.1.Final.jar:1.3.1.Final] at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) [keycloak-undertow-adapter-1.3.1.Final.jar:1.3.1.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.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_72-internal] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_72-internal] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_72-internal]

9 years, 4 months

3
11
0 / 0

UPS Device Registration Endpoints

by Luke Holmquist

thats right folks, i'm asking this question on a Friday before a Holiday weekend(US) at 3:52(est) i've started to implement the Device registration endpoints in node and was just wondering what the id is here in this header -v -H "Accept: application/json" -H "Content-type: application/json" -H "aerogear-push-id: someid" is it something specific, or just a random number/alpha-numeric thingy here is the doc link for reference: https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/#246535932 I've also decided to create this as a separate module instead of including it in the node admin client here: https://github.com/bucharest-gold/unifiedpush-admin-client mostly becuase these registration endpoints don't needed to be KC authenticated. and they could also be used on a IOT device or something that runs node that has webpush/simplePush or some new crazy protocol. -Luke

9 years, 4 months

3
5
0 / 0

Unexpected error running Liquibase: Precondition Error

by asimsinan

I am trying to set up aerogear ups. I executed all the commands successfully till creating atabase schema. After I run ./bin/ups-migrator update, I get an error saying that Unexpected error running Liquibase: Precondition Error. What may be the problem? -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Unexpected-error-running-Liqu... Sent from the aerogear-users mailing list archive at Nabble.com.

9 years, 4 months

3
11
0 / 0

Not able to receive OpenIDClaim and accesstoken from redirecturi in iOS app

by ashish

I configured keycloak and iOS app I am able to connect with iOS app to keycloak. (Oauth2.0 aerogear SDK and keycloak 1.9.3) After successful login safari browser redirects to app where I should be able to get access token. response comes as nil in login call back method. Below is the code which I run let keycloakConfig = Config(base: "http://kc.dev.com:8080", authzEndpoint: "auth/realms/SharedServices/protocol/openid-connect/auth", redirectURL:"fcapp:/", accessTokenEndpoint: "/auth/realms/SharedServices/protocol/openid-connect/token", clientId: "Mobile", refreshTokenEndpoint: "/auth/realms/SharedServices/protocol/openid-connect/token/refresh", revokeTokenEndpoint: "/auth/realms/SharedServices/protocol/openid-connect/token/revoke" ) keycloakConfig.isWebView = false let http = Http() var gdModule = AccountManager.addAccount(keycloakConfig, moduleClass: KeycloakOAuth2Module.self) // gdModule = KeycloakOAuth2Module(config: keycloakConfig, session: UntrustedMemoryOAuth2Session(accountId: "ACCOUNT_FOR_CLIENTID_(keycloakConfig.clientId)")) http.authzModule = gdModule gdModule.login {(accessToken: AnyObject?, claims: OpenIDClaim?, error: NSError?) in print(accessToken) // Comes nil how can I get access token?? print(claims?.description) // Comes nil print(error) // comes as errorcode =0 self.userInfo = claims if let userInfo = claims { if let name = userInfo.name { print(name) } } } -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Not-able-to-receive-OpenIDCla... Sent from the aerogear-users mailing list archive at Nabble.com.

9 years, 4 months

1
1
0 / 0

KeychainWrapper

by ashish

Can someone please guide on using keychainwrapper in AeroGearOAuth2 let token = KeychainWrapper.objectForKey("Access token") These docs looks old https://aerogear.org/docs/specs/aerogear-ios-oauth2/Classes/KeychainWrap.... Not sure which are the right keys to get correct values from keychainwrapper Thanks Ashish -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/KeychainWrapper-tp680.html Sent from the aerogear-users mailing list archive at Nabble.com.

9 years, 4 months

1
1
0 / 0

USP with external Keycloak

by Anton

Hi Can somone please help us. We are looking for how we can use UPS with an already existing KC server. We could not find any documentation on this. Kind regards Anton

9 years, 4 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

Aerogear-users May 2016