From vfbsilva at gmail.com Mon Jul 3 14:17:22 2017 From: vfbsilva at gmail.com (vfbsilva) Date: Mon, 3 Jul 2017 11:17:22 -0700 (MST) Subject: [Aerogear-users] Problems deplying aerogear in kubernetes with wildfly eap In-Reply-To: <1498677793883-1134.post@n5.nabble.com> References: <1498677793883-1134.post@n5.nabble.com> Message-ID: <1499105842041-1135.post@n5.nabble.com> Summers, seems I was missing: /./bin/ups-migrator update/ It was not clear from me when building the image I needed to perform this step. Now I'm facing some SSL miss configuration, whenever I try to acess /ag-push/ or /auth I get an SSL error: /Exception handling request to /ag-push/: java.lang.RuntimeException: Unable to resolve realm public key remotely/ the image ships with self-signed certs under: *standalone/configuration/certs/* I've ran certificate.sh providing my domain name and adding it to standalone.xml still seems it is not importing my key. What am I missing? -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Problems-deplying-aerogear-in-kubernetes-with-wildfly-eap-tp1132p1135.html Sent from the aerogear-users mailing list archive at Nabble.com. From supittma at redhat.com Wed Jul 5 08:35:01 2017 From: supittma at redhat.com (Summers Pittman) Date: Wed, 5 Jul 2017 08:35:01 -0400 Subject: [Aerogear-users] Problems deplying aerogear in kubernetes with wildfly eap In-Reply-To: <1499105842041-1135.post@n5.nabble.com> References: <1498677793883-1134.post@n5.nabble.com> <1499105842041-1135.post@n5.nabble.com> Message-ID: On Mon, Jul 3, 2017 at 2:17 PM, vfbsilva wrote: > Summers, seems I was missing: > > /./bin/ups-migrator update/ > > It was not clear from me when building the image I needed to perform this > step. Now I'm facing some SSL miss configuration, whenever I try to acess > /ag-push/ or /auth I get an SSL error: > > /Exception handling request to /ag-push/: java.lang.RuntimeException: > Unable > to resolve realm public key remotely/ > > > the image ships with self-signed certs under: > > *standalone/configuration/certs/* > > I've ran certificate.sh providing my domain name and adding it to > standalone.xml still seems it is not importing my key. What am I missing? > > > Looping back in for posterity : The ag-auth deployment isn't running in Kubernetes for some reason. The error you are getting is from the auth system not deploying not from SSL. The realm public key is a configuration option there. I've created https://issues.jboss.org/browse/AEROGEAR-1747 with more details. However that issue may never get fixed because we are splitting up auth from the deployed package "soon". Since auth will be deployed separately the problem just won't exist any more. Summers > > > > -- > View this message in context: http://aerogear-users.1116366. > n5.nabble.com/Aerogear-users-Problems-deplying-aerogear-in- > kubernetes-with-wildfly-eap-tp1132p1135.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/20170705/a039a538/attachment.html From vfbsilva at gmail.com Wed Jul 5 11:43:19 2017 From: vfbsilva at gmail.com (vfbsilva) Date: Wed, 5 Jul 2017 08:43:19 -0700 (MST) Subject: [Aerogear-users] Problems deplying aerogear in kubernetes with wildfly eap In-Reply-To: References: <1498677793883-1134.post@n5.nabble.com> <1499105842041-1135.post@n5.nabble.com> Message-ID: <1499269399875-1137.post@n5.nabble.com> How can it work in jboss and do not work on kubernetes as containers are "like" real machines? What is the difference in the code run inside of a pod vs a real machine? -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Problems-deplying-aerogear-in-kubernetes-with-wildfly-eap-tp1132p1137.html Sent from the aerogear-users mailing list archive at Nabble.com. From supittma at redhat.com Wed Jul 5 13:42:29 2017 From: supittma at redhat.com (Summers Pittman) Date: Wed, 5 Jul 2017 13:42:29 -0400 Subject: [Aerogear-users] Problems deplying aerogear in kubernetes with wildfly eap In-Reply-To: References: <1498677793883-1134.post@n5.nabble.com> <1499105842041-1135.post@n5.nabble.com> Message-ID: On Wed, Jul 5, 2017 at 8:35 AM, Summers Pittman wrote: > > > On Mon, Jul 3, 2017 at 2:17 PM, vfbsilva wrote: > >> Summers, seems I was missing: >> >> /./bin/ups-migrator update/ >> >> It was not clear from me when building the image I needed to perform this >> step. Now I'm facing some SSL miss configuration, whenever I try to acess >> /ag-push/ or /auth I get an SSL error: >> >> /Exception handling request to /ag-push/: java.lang.RuntimeException: >> Unable >> to resolve realm public key remotely/ >> >> >> the image ships with self-signed certs under: >> >> *standalone/configuration/certs/* >> >> I've ran certificate.sh providing my domain name and adding it to >> standalone.xml still seems it is not importing my key. What am I missing? >> >> >> > Looping back in for posterity : > > The ag-auth deployment isn't running in Kubernetes for some reason. The > error you are getting is from the auth system not deploying not from SSL. > The realm public key is a configuration option there. I've created > https://issues.jboss.org/browse/AEROGEAR-1747 with more details. However > that issue may never get fixed because we are splitting up auth from the > deployed package "soon". Since auth will be deployed separately the > problem just won't exist any more. > > So it looks like resetting my mySQL databases solved the problem I was having and UPS deployed normally in kubernetes. I also switched to the aerogear/unifiedpush-wildfly-dev image which may or may not have affected the result as well. > Summers > > >> >> >> >> -- >> View this message in context: http://aerogear-users.1116366. >> n5.nabble.com/Aerogear-users-Problems-deplying-aerogear-in-k >> ubernetes-with-wildfly-eap-tp1132p1135.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/20170705/ae056c2e/attachment.html From mitja.kotnik at cloud.si Thu Jul 6 02:44:17 2017 From: mitja.kotnik at cloud.si (Mitja Jesenicnik Kotnik) Date: Thu, 6 Jul 2017 08:44:17 +0200 Subject: [Aerogear-users] Android AeroGear Auth 3.1.1 Message-ID: Hello, now I've updated my version from Android AG Auth 3.1.0 to 3.1.1 and it stopped working. If I revert back it works again, but at 3.1.1 it returns this stackTrace: 07-06 06:40:33.690 5751-5751/com.kumuluz.ccm.android.sample D/KeycloakHelper: Keycloak failure: AuthorizationException{error=invalid_request} 07-06 06:40:33.690 5751-5751/com.kumuluz.ccm.android.sample W/System.err: AuthorizationException{error=invalid_request} 07-06 06:40:33.690 5751-5751/com.kumuluz.ccm.android.sample W/System.err: at org.jboss.aerogear.android.authorization.oauth2.OAuth2AuthzService.runAccountAction(OAuth2AuthzService.java:278) 07-06 06:40:33.690 5751-5751/com.kumuluz.ccm.android.sample W/System.err: at org.jboss.aerogear.android.authorization.oauth2.OAuth2AuthzService.exchangeAuthorizationCodeForAccessToken(OAuth2AuthzService.java:208) 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: at org.jboss.aerogear.android.authorization.oauth2.OAuth2AuthzService.fetchAccessToken(OAuth2AuthzService.java:93) 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: at org.jboss.aerogear.android.authorization.oauth2.OAuth2FetchAccess$1.doInBackground(OAuth2FetchAccess.java:51) 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: at android.os.AsyncTask$2.call(AsyncTask.java:304) 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: at java.util.concurrent.FutureTask.run(FutureTask.java:237) 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133) 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607) 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: at java.lang.Thread.run(Thread.java:761) 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample D/LoginActivity: Login failed! Best regards, MK -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170706/ef9f898c/attachment.html From mitja.kotnik at cloud.si Thu Jul 6 03:30:11 2017 From: mitja.kotnik at cloud.si (Mitja Jesenicnik Kotnik) Date: Thu, 6 Jul 2017 09:30:11 +0200 Subject: [Aerogear-users] Android AeroGear Auth 3.1.1 In-Reply-To: References: Message-ID: And this is the response, even though when I debug the app the grand_type is defined. {"error":"invalid_request","error_description":"Missing form parameter: grant_type"} On Thu, Jul 6, 2017 at 8:44 AM, Mitja Jesenicnik Kotnik < mitja.kotnik at cloud.si> wrote: > Hello, > > now I've updated my version from Android AG Auth 3.1.0 to 3.1.1 and it > stopped working. If I revert back it works again, but at 3.1.1 it returns > this stackTrace: > > 07-06 06:40:33.690 5751-5751/com.kumuluz.ccm.android.sample > D/KeycloakHelper: Keycloak failure: AuthorizationException{error= > invalid_request} > 07-06 06:40:33.690 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > AuthorizationException{error=invalid_request} > 07-06 06:40:33.690 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at org.jboss.aerogear.android.authorization.oauth2.OAuth2AuthzService. > runAccountAction(OAuth2AuthzService.java:278) > 07-06 06:40:33.690 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at org.jboss.aerogear.android.authorization.oauth2.OAuth2AuthzService. > exchangeAuthorizationCodeForAccessToken(OAuth2AuthzService.java:208) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at org.jboss.aerogear.android.authorization.oauth2.OAuth2AuthzService. > fetchAccessToken(OAuth2AuthzService.java:93) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at org.jboss.aerogear.android.authorization.oauth2. > OAuth2FetchAccess$1.doInBackground(OAuth2FetchAccess.java:51) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at android.os.AsyncTask$2.call(AsyncTask.java:304) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at java.util.concurrent.FutureTask.run(FutureTask.java:237) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at java.util.concurrent.ThreadPoolExecutor.runWorker( > ThreadPoolExecutor.java:1133) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:607) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at java.lang.Thread.run(Thread.java:761) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample > D/LoginActivity: Login failed! > > Best regards, > MK > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20170706/625e8b14/attachment-0001.html From supittma at redhat.com Thu Jul 6 07:23:12 2017 From: supittma at redhat.com (Summers Pittman) Date: Thu, 6 Jul 2017 07:23:12 -0400 Subject: [Aerogear-users] Android AeroGear Auth 3.1.1 In-Reply-To: References: Message-ID: On Thu, Jul 6, 2017 at 2:44 AM, Mitja Jesenicnik Kotnik < mitja.kotnik at cloud.si> wrote: > Hello, > > now I've updated my version from Android AG Auth 3.1.0 to 3.1.1 and it > stopped working. If I revert back it works again, but at 3.1.1 it returns > this stackTrace: > Sounds like a regression. We've made a JIRA https://issues.jboss.org/browse/AEROGEAR-1748 to track it, keep your eyes peeled. > > 07-06 06:40:33.690 5751-5751/com.kumuluz.ccm.android.sample > D/KeycloakHelper: Keycloak failure: AuthorizationException{error= > invalid_request} > 07-06 06:40:33.690 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > AuthorizationException{error=invalid_request} > 07-06 06:40:33.690 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at org.jboss.aerogear.android.authorization.oauth2.OAuth2AuthzService. > runAccountAction(OAuth2AuthzService.java:278) > 07-06 06:40:33.690 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at org.jboss.aerogear.android.authorization.oauth2.OAuth2AuthzService. > exchangeAuthorizationCodeForAccessToken(OAuth2AuthzService.java:208) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at org.jboss.aerogear.android.authorization.oauth2.OAuth2AuthzService. > fetchAccessToken(OAuth2AuthzService.java:93) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at org.jboss.aerogear.android.authorization.oauth2. > OAuth2FetchAccess$1.doInBackground(OAuth2FetchAccess.java:51) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at android.os.AsyncTask$2.call(AsyncTask.java:304) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at java.util.concurrent.FutureTask.run(FutureTask.java:237) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at java.util.concurrent.ThreadPoolExecutor.runWorker( > ThreadPoolExecutor.java:1133) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:607) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample W/System.err: > at java.lang.Thread.run(Thread.java:761) > 07-06 06:40:33.691 5751-5751/com.kumuluz.ccm.android.sample > D/LoginActivity: Login failed! > > Best regards, > MK > > _______________________________________________ > 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/20170706/e63519d5/attachment.html From vfbsilva at gmail.com Fri Jul 7 16:16:05 2017 From: vfbsilva at gmail.com (vfbsilva) Date: Fri, 7 Jul 2017 13:16:05 -0700 (MST) Subject: [Aerogear-users] Problems deplying aerogear in kubernetes with wildfly eap In-Reply-To: References: <1498677793883-1134.post@n5.nabble.com> <1499105842041-1135.post@n5.nabble.com> Message-ID: <1499458565810-1142.post@n5.nabble.com> Summers I circumvented the problem here. Seems the application doesn't like my ingress: /ingress.yaml kind: Ingress apiVersion: extensions/v1beta1 metadata: annotations: ingress.kubernetes.io/whitelist-source-range: 10.0.0.0/8,127.0.0.1/32 ingress.kubernetes.io/proxy-body-size: 1m ingress.kubernetes.io/rewrite-target: / ingress.kubernetes.io/ssl-redirect: "true" name: aerogear namespace: blah-v spec: rules: - host:myhost.com http: paths: - backend: serviceName: aerogear servicePort: 8080 path: / tls: - hosts: - myhost.com/ I've ran the same image same databases without this ingress pointing a dns directly to it. And it works. So now we know where is the problem still I cannot grasp its reason. Summers Pittman wrote > On Wed, Jul 5, 2017 at 8:35 AM, Summers Pittman < > supittma@ > > wrote: > >> >> >> On Mon, Jul 3, 2017 at 2:17 PM, vfbsilva < > vfbsilva@ > > wrote: >> >>> Summers, seems I was missing: >>> >>> /./bin/ups-migrator update/ >>> >>> It was not clear from me when building the image I needed to perform >>> this >>> step. Now I'm facing some SSL miss configuration, whenever I try to >>> acess >>> /ag-push/ or /auth I get an SSL error: >>> >>> /Exception handling request to /ag-push/: java.lang.RuntimeException: >>> Unable >>> to resolve realm public key remotely/ >>> >>> >>> the image ships with self-signed certs under: >>> >>> *standalone/configuration/certs/* >>> >>> I've ran certificate.sh providing my domain name and adding it to >>> standalone.xml still seems it is not importing my key. What am I >>> missing? >>> >>> >>> >> Looping back in for posterity : >> >> The ag-auth deployment isn't running in Kubernetes for some reason. The >> error you are getting is from the auth system not deploying not from SSL. >> The realm public key is a configuration option there. I've created >> https://issues.jboss.org/browse/AEROGEAR-1747 with more details. However >> that issue may never get fixed because we are splitting up auth from the >> deployed package "soon". Since auth will be deployed separately the >> problem just won't exist any more. >> >> > So it looks like resetting my mySQL databases solved the problem I was > having and UPS deployed normally in kubernetes. I also switched to the > aerogear/unifiedpush-wildfly-dev image which may or may not have affected > the result as well. > > >> Summers >> >> >>> >>> >>> >>> -- >>> View this message in context: http://aerogear-users.1116366. >>> n5.nabble.com/Aerogear-users-Problems-deplying-aerogear-in-k >>> ubernetes-with-wildfly-eap-tp1132p1135.html >>> Sent from the aerogear-users mailing list archive at Nabble.com. >>> _______________________________________________ >>> Aerogear-users mailing list >>> > Aerogear-users at .jboss >>> https://lists.jboss.org/mailman/listinfo/aerogear-users >>> >> >> > > _______________________________________________ > Aerogear-users mailing list > Aerogear-users at .jboss > https://lists.jboss.org/mailman/listinfo/aerogear-users -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Problems-deplying-aerogear-in-kubernetes-with-wildfly-eap-tp1132p1142.html Sent from the aerogear-users mailing list archive at Nabble.com. From xfdeng at hotmail.com Mon Jul 31 19:11:13 2017 From: xfdeng at hotmail.com (jeff01) Date: Mon, 31 Jul 2017 16:11:13 -0700 (MST) Subject: [Aerogear-users] Aerogear annual support license cost? Message-ID: <1501542673308-1143.post@n5.nabble.com> Sorry if this is not the right the question here. Where can I get a quote for Aerogear annual support license? We wanted to make sure we have a place to quickly resolve the issue in production in case we have any issues after we move Aerogear to the real business environment. Thanks for any help you may provide. -- View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-annual-support-license-cost-tp1143.html Sent from the aerogear-users mailing list archive at Nabble.com.