From corinnekrych at gmail.com  Wed May  4 02:41:35 2016
From: corinnekrych at gmail.com (Corinne Krych)
Date: Wed, 4 May 2016 08:41:35 +0200
Subject: [Aerogear-users] AeroGear SDK integration with Keycloak
In-Reply-To: <CAL8vO=c9TnF7ia2OMTnwqPJmVv2vPNJDx7VkrNEQKokV_m7Wsg@mail.gmail.com>
References: <4C1D8037-6EBE-4B33-9EC4-391C68259BD5@indegene.com>
	<CADF=h2soKNyRo-qfTRfWcwXnkKeB43A08-MspD9H5CaGUPeKEA@mail.gmail.com>
	<CAL8vO=c9TnF7ia2OMTnwqPJmVv2vPNJDx7VkrNEQKokV_m7Wsg@mail.gmail.com>
Message-ID: <CAL8vO=eGhDuJYBH=H+KY4g_LGxPsmFgbfyhWFZ76PPjdrLC1Qg@mail.gmail.com>

Hello Ashish,

PR tested and merged.
aerogear-ios-oauth2 and Shoot app in aerogear-ios-cookbook have been
updated to fir latest Keycloak release.
A new release of AeroGearOAuth2 will be announced soon. In the mean time
fetch the pod from github master branch.

Let us know if you still have issues.
++
Corinne

On 29 April 2016 at 13:57, Corinne Krych <corinnekrych at gmail.com> wrote:

> Hello Ashish,
>
> Could you test this PR [1]?
> As Passos mentioned the 404 error must be due to the endpoint changes.
>
> ++
> Corinne
> [1] https://github.com/aerogear/aerogear-ios-oauth2/pull/43
>
> On 28 April 2016 at 18:01, Daniel Passos <dpassos at redhat.com> wrote:
>
>> Hi
>>
>> Are you getting this error when you are firing a request to KC server
>> from your app?
>>
>> ```
>>
>> 17:01:31,549 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-1) RESTEASY002010: Failed to execute: javax.ws.rs.NotFoundException: HTTP 404 Not Found
>>
>> ```
>>
>> I'm not 100% sure (didn't have time to test) but I think the problem is,
>> KC 1.9.1 are using different endpoints and the iOS app was not updated yet.
>>
>> Our cookbook backend[1] was updated to 1.9.1 by the community[2] weeks ago
>>
>> Unfortunately he updated only the Android app[3] to the new endpoints
>>
>> Can you check the Android PR[3] and see if you change that in the iOS app
>> it works?
>>
>> [1]
>> https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot
>> [2] https://github.com/aerogear/aerogear-backend-cookbook/pull/29
>> [3] https://github.com/aerogear/aerogear-android-cookbook/pull/56
>>
>>
>>
>>
>>
>>
>>
>> On Thu, Apr 28, 2016 at 8:44 AM, Ashish Pandita <
>> Ashish.Pandita at indegene.com> wrote:
>>
>>> Hi All,
>>>
>>> I am having some trouble using aerogear to connect keycloak locally. I
>>> am using shoot example I did the following things
>>> 1) installed pods on shoot&share
>>> https://github.com/aerogear/aerogear-ios-cookbook/tree/0.3.0/Shoot
>>> 2) installed the key cloak ver keycloak-1.9.2.Final (
>>> https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot)
>>> I can access the admin console in browser imported the realm configuration
>>> https://github.com/aerogear/aerogear-backend-cookbook/blob/master/Shoot/configuration/shoot-realm.json
>>> 3) I run the server attached is the log and here is the terminal rec
>>> https://asciinema.org/a/7xhosmb63kn9tnvn99gnh5mbm
>>> 4) I am not able to login to keycloak. I am getting errors in console
>>> when keycloak launches the web view can you please help what need to be
>>> done to resolve it or guide to proper resource.
>>>
>>> here is the Aerogear API which I am using
>>>
>>>  @IBAction func shareWithKeycloak() {
>>>
>>>
>>>         let keycloakHost = "http://localhost:8080"
>>>         let keycloakConfig = KeycloakConfig(
>>>             clientId: "shoot-third-party",
>>>             host: keycloakHost,
>>>             realm: "shoot-realm")
>>>         // If you want to use embedded web view uncomment
>>>           keycloakConfig.isWebView = true
>>>
>>>
>>>         // Workaround issue on Keychain
>>> https://forums.developer.apple.com/message/23323
>>>         let gdModule = KeycloakOAuth2Module(config: keycloakConfig,
>>> session: UntrustedMemoryOAuth2Session(accountId: "ACCOUNT_FOR_CLIENTID_\
>>> (keycloakConfig.clientId)"))
>>>
>>>
>>>         // let gdModule =
>>> AccountManager.addKeycloakAccount(keycloakConfig)
>>>         self.http.authzModule = gdModule
>>>        /* gdModule.login { (response, token, error) in
>>>
>>>
>>>             print(response)
>>>             print(token)
>>>             print(error)
>>>         } */
>>>
>>>
>>>
>>>
>>>          print("Perform photo upload with Keycloak")
>>>
>>>
>>>
>>>
>>>        self.performUpload("\(keycloakHost)/shoot/rest/photos",
>>> parameters: self.extractImageAsMultipartParams())
>>>
>>>     }
>>>
>>>     func performUpload(url: String, parameters: [String: AnyObject]?) {
>>>
>>>
>>>
>>>
>>>         self.http.request(HttpMethod.POST, path: url, parameters:
>>> parameters, credential: nil, responseSerializer: nil) { (response,
>>> error) in
>>>             if (error != nil) {
>>>                 self.presentAlert("Error", message: error!.
>>> localizedDescription)
>>>             } else {
>>>                 self.presentAlert("Success", message: "Successfully
>>> uploaded!")
>>>             }
>>>         }
>>>
>>>
>>>         /*
>>>
>>>
>>>         self.http.POST(url, parameters: parameters, completionHandler:
>>> {(response, error) in
>>>             if (error != nil) {
>>>                 self.presentAlert("Error", message:
>>> error!.localizedDescription)
>>>             } else {
>>>                 self.presentAlert("Success", message: "Successfully
>>> uploaded!")
>>>             }
>>>         })
>>>
>>>
>>>             */
>>>     }
>>>
>>>
>>>
>>> Disclaimer : This message and any attachments are solely for the
>>> intended recipient and may contain confidential or privileged information.
>>> If you are not the intended recipient, any disclosure, copying, use, or
>>> distribution of the information included in this message and any
>>> attachments is prohibited. If you have received this communication in
>>> error, please notify us by reply e-mail to IT at Indegene.com and
>>> immediately and permanently delete this message and any attachments. Any
>>> views expressed in this mail are not necessarily the views of INDEGENE.
>>> Thank you.
>>>
>>> _______________________________________________
>>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160504/21c8543d/attachment.html 

From David.Walto at baystatehealth.org  Wed May  4 16:53:00 2016
From: David.Walto at baystatehealth.org (Walto, David)
Date: Wed, 4 May 2016 16:53:00 -0400
Subject: [Aerogear-users] JBoss Unified Push - iOS registers but does not
 receive notifications
Message-ID: <0BBC8B85145220449B53DE768FDA802A162B02BD9B@bhsexc12.bhs.org>

I have a JBoss Unified Push account with Android and iOS variants. The Android works fine, the device registers and receives notifications.

On my iOS variant, when I start my app the device registers and I can see it as an installation on the Unified Push applications page. But when I Send a Push, the device never gets the notification, and the installation goes away. I would think the registration of the device being removed would be a clue on the issue.

Can you spread some light on what might be causing this.

Thanks

David Walto
Senior Application Engineer | EMR Engineering and Integration
Baystate Health | Information & Technology

----------------------------------------------------------------------
Please view our annual report at http://www.bhannualreport.org
 

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 https://www.baystatehealth.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160504/e586a92a/attachment-0001.html 

From matzew at apache.org  Wed May  4 17:59:59 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 4 May 2016 23:59:59 +0200
Subject: [Aerogear-users] JBoss Unified Push - iOS registers but does
 not receive notifications
In-Reply-To: <0BBC8B85145220449B53DE768FDA802A162B02BD9B@bhsexc12.bhs.org>
References: <0BBC8B85145220449B53DE768FDA802A162B02BD9B@bhsexc12.bhs.org>
Message-ID: <CAAg5f2R6q3qpN7RbFK_jXQ7VMzwCgf0oa92Z-etWUXDWaJ+GdQ@mail.gmail.com>

likely there is s wrong certificate in place

On Wednesday, 4 May 2016, Walto, David <David.Walto at baystatehealth.org>
wrote:

> I have a JBoss Unified Push account with Android and iOS variants. The
> Android works fine, the device registers and receives notifications.
>
>
>
> On my iOS variant, when I start my app the device registers and I can see
> it as an installation on the Unified Push applications page. But when I
> Send a Push, the device never gets the notification, and the installation
> goes away. I would think the registration of the device being removed would
> be a clue on the issue.
>
>
>
> Can you spread some light on what might be causing this.
>
>
>
> Thanks
>
>
>
> *David Walto*
>
> *Senior Application Engineer | EMR Engineering and Integration*
>
> *Baystate Health | Information & Technology*
>
>
> ------------------------------
> Please view our annual report at http://www.bhannualreport.org
>
>
> 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 https://www.baystatehealth.org.
>


-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160504/78b47adb/attachment.html 

From David.Walto at baystatehealth.org  Thu May  5 09:51:55 2016
From: David.Walto at baystatehealth.org (Walto, David)
Date: Thu, 5 May 2016 09:51:55 -0400
Subject: [Aerogear-users] JBoss Unified Push - iOS registers but does
 not receive notifications
In-Reply-To: <CAAg5f2R6q3qpN7RbFK_jXQ7VMzwCgf0oa92Z-etWUXDWaJ+GdQ@mail.gmail.com>
References: <0BBC8B85145220449B53DE768FDA802A162B02BD9B@bhsexc12.bhs.org>
	<CAAg5f2R6q3qpN7RbFK_jXQ7VMzwCgf0oa92Z-etWUXDWaJ+GdQ@mail.gmail.com>
Message-ID: <0BBC8B85145220449B53DE768FDA802A162B02BE77@bhsexc12.bhs.org>

Thanks, that was it, I was able to get it working after regenerating the certificate.

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

From: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] On Behalf Of Matthias Wessendorf
Sent: Wednesday, May 04, 2016 6:00 PM
To: aerogear-users at lists.jboss.org
Subject: Re: [Aerogear-users] JBoss Unified Push - iOS registers but does not receive notifications

likely there is s wrong certificate in place

On Wednesday, 4 May 2016, Walto, David <David.Walto at baystatehealth.org<mailto:David.Walto at baystatehealth.org>> wrote:
I have a JBoss Unified Push account with Android and iOS variants. The Android works fine, the device registers and receives notifications.

On my iOS variant, when I start my app the device registers and I can see it as an installation on the Unified Push applications page. But when I Send a Push, the device never gets the notification, and the installation goes away. I would think the registration of the device being removed would be a clue on the issue.

Can you spread some light on what might be causing this.

Thanks

David Walto
Senior Application Engineer | EMR Engineering and Integration
Baystate Health | Information & Technology

________________________________
Please view our annual report at http://www.bhannualreport.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.bhannualreport.org&d=BQMFaQ&c=BLF1codk7grETTA02F6JwR5DiXMTPyNdcZpbXT_1iEc&r=LbJn1w7LZEE3M7-Y0PXb-GWupGXi6Xr5oEcvyz5Hzw4&m=rbeVBDtfbko57oeumSbJtWIiHB-DJIrg-7PMGtyGxA0&s=EJTfpd6OsJKVlSAC_rfMrzSEiH0-b3Cipd5EudOlIqM&e=>


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 https://www.baystatehealth.org.


--
Sent from Gmail Mobile

----------------------------------------------------------------------
Please view our annual report at http://www.bhannualreport.org
 

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 https://www.baystatehealth.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160505/a8c8f363/attachment.html 

From lholmqui at redhat.com  Thu May  5 11:14:42 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 5 May 2016 11:14:42 -0400
Subject: [Aerogear-users] UnifiedPush Node sender move to Promises
Message-ID: <CALD3Fd0N2Nvq32ehMtO8UAXTBQ35uFF9Od037G9-TAgE3YpQLA@mail.gmail.com>

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160505/f80aaeb4/attachment-0001.html 

From matzew at apache.org  Thu May  5 13:37:47 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 5 May 2016 19:37:47 +0200
Subject: [Aerogear-users] UnifiedPush Node sender move to Promises
In-Reply-To: <CALD3Fd0N2Nvq32ehMtO8UAXTBQ35uFF9Od037G9-TAgE3YpQLA@mail.gmail.com>
References: <CALD3Fd0N2Nvq32ehMtO8UAXTBQ35uFF9Od037G9-TAgE3YpQLA@mail.gmail.com>
Message-ID: <CAAg5f2SdUCCXKRf3Ktdhs0JZHSr5OjtxJC24Fngz+XY5Noe_qw@mail.gmail.com>

I think it would be good for the community to move forward and use latest
technology. Node 0.12 is already very old, given the current version is 6.

How about getting promisses in, and afterwards release this as a 1.0.0
release ?

On Thu, May 5, 2016 at 5:14 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> 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
>
>
>
>
>
> _______________________________________________
> 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/20160505/03863383/attachment.html 

From lholmqui at redhat.com  Thu May  5 13:42:52 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 5 May 2016 13:42:52 -0400
Subject: [Aerogear-users] UnifiedPush Node sender move to Promises
In-Reply-To: <CAAg5f2SdUCCXKRf3Ktdhs0JZHSr5OjtxJC24Fngz+XY5Noe_qw@mail.gmail.com>
References: <CALD3Fd0N2Nvq32ehMtO8UAXTBQ35uFF9Od037G9-TAgE3YpQLA@mail.gmail.com>
	<CAAg5f2SdUCCXKRf3Ktdhs0JZHSr5OjtxJC24Fngz+XY5Noe_qw@mail.gmail.com>
Message-ID: <CALD3Fd0a7+gk4dV6ABvj=6-XWh0+qBg_qmAY62jTay1NnCvABw@mail.gmail.com>

On Thu, May 5, 2016 at 1:37 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> I think it would be good for the community to move forward and use latest
> technology. Node 0.12 is already very old, given the current version is 6.
>
> How about getting promisses in, and afterwards release this as a 1.0.0
> release ?
>

i think this sounds like a plan,

/me goes and creates a JIRA

>
> On Thu, May 5, 2016 at 5:14 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> 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
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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/20160505/7b3e69c9/attachment.html 

From lholmqui at redhat.com  Thu May  5 13:46:15 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 5 May 2016 13:46:15 -0400
Subject: [Aerogear-users] UnifiedPush Node sender move to Promises
In-Reply-To: <CALD3Fd0a7+gk4dV6ABvj=6-XWh0+qBg_qmAY62jTay1NnCvABw@mail.gmail.com>
References: <CALD3Fd0N2Nvq32ehMtO8UAXTBQ35uFF9Od037G9-TAgE3YpQLA@mail.gmail.com>
	<CAAg5f2SdUCCXKRf3Ktdhs0JZHSr5OjtxJC24Fngz+XY5Noe_qw@mail.gmail.com>
	<CALD3Fd0a7+gk4dV6ABvj=6-XWh0+qBg_qmAY62jTay1NnCvABw@mail.gmail.com>
Message-ID: <CALD3Fd1=F65fEFUoCdFWzxLGU4hmV3fosutUgzO6YpyW4H96Ow@mail.gmail.com>

for those following along at home:

https://issues.jboss.org/browse/AGPUSH-1621

On Thu, May 5, 2016 at 1:42 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

>
>
> On Thu, May 5, 2016 at 1:37 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> I think it would be good for the community to move forward and use latest
>> technology. Node 0.12 is already very old, given the current version is 6.
>>
>> How about getting promisses in, and afterwards release this as a 1.0.0
>> release ?
>>
>
> i think this sounds like a plan,
>
> /me goes and creates a JIRA
>
>>
>> On Thu, May 5, 2016 at 5:14 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>> 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
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/20160505/e921bb9b/attachment.html 

From ashishkumarpandita at gmail.com  Fri May  6 04:01:12 2016
From: ashishkumarpandita at gmail.com (ashish)
Date: Fri, 6 May 2016 01:01:12 -0700 (MST)
Subject: [Aerogear-users] Not able to receive OpenIDClaim and accesstoken
 from redirecturi in iOS app
Message-ID: <1462521672470-639.post@n5.nabble.com>

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-OpenIDClaim-and-accesstoken-from-redirecturi-in-iOS-app-tp639.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From lholmqui at redhat.com  Mon May  9 16:19:03 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Mon, 9 May 2016 16:19:03 -0400
Subject: [Aerogear-users] deploy failure for Master
Message-ID: <CALD3Fd2ZMbDAosdSFYkFqn4hFJy-TrHj7Y6M3qbFnoH6wWv_bg@mail.gmail.com>

so i'm trying to deploy what is currently on master to wildfly 9(also tried
10) and i'm getting this error:

https://gist.github.com/lholmquist/6743191e4c4f225dac7e8e16e86f09fc


i've copied the h2 db deployment script to the wildly deployment
directory,  manually copied the  auth-server and ag-push war files to the
wildlfy deployment directory from their respective target directories,

started with "./bin/standalone.sh -c standalone-full.xml -b 0.0.0.0"

perhaps i'm missing a step?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160509/b7f51bea/attachment.html 

From matzew at apache.org  Tue May 10 00:11:14 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 May 2016 06:11:14 +0200
Subject: [Aerogear-users] [aerogear-dev] deploy failure for Master
In-Reply-To: <CALD3Fd2ZMbDAosdSFYkFqn4hFJy-TrHj7Y6M3qbFnoH6wWv_bg@mail.gmail.com>
References: <CALD3Fd2ZMbDAosdSFYkFqn4hFJy-TrHj7Y6M3qbFnoH6wWv_bg@mail.gmail.com>
Message-ID: <CAAg5f2S9SphzfsS60cFAKJRVyWjPAXbL_J_oEefsi4r4x7F24Q@mail.gmail.com>

Hi Luke,

besides the DB CLI, you need to configure JMS, using this CLI:
https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/configuration

Note, the JMS bits are tied to WF-10.


On Mon, May 9, 2016 at 10:19 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> so i'm trying to deploy what is currently on master to wildfly 9(also
> tried 10) and i'm getting this error:
>
> https://gist.github.com/lholmquist/6743191e4c4f225dac7e8e16e86f09fc
>
>
> i've copied the h2 db deployment script to the wildly deployment
> directory,  manually copied the  auth-server and ag-push war files to the
> wildlfy deployment directory from their respective target directories,
>
> started with "./bin/standalone.sh -c standalone-full.xml -b 0.0.0.0"
>
> perhaps i'm missing a step?
>
> _______________________________________________
> 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/20160510/27b3235f/attachment.html 

From lholmqui at redhat.com  Tue May 10 08:39:48 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Tue, 10 May 2016 08:39:48 -0400
Subject: [Aerogear-users] [aerogear-dev] deploy failure for Master
In-Reply-To: <CAAg5f2S9SphzfsS60cFAKJRVyWjPAXbL_J_oEefsi4r4x7F24Q@mail.gmail.com>
References: <CALD3Fd2ZMbDAosdSFYkFqn4hFJy-TrHj7Y6M3qbFnoH6wWv_bg@mail.gmail.com>
	<CAAg5f2S9SphzfsS60cFAKJRVyWjPAXbL_J_oEefsi4r4x7F24Q@mail.gmail.com>
Message-ID: <CALD3Fd0xvzuoCWbUEa_S=Yp6CsXVFbzivioJJ2RBOGxCHeOVSQ@mail.gmail.com>

ah yes, that did it.

I suppose i should have RTFM,  i usually look at the readme on GH, i'm
wondering if there should be something there also?

On Tue, May 10, 2016 at 12:11 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi Luke,
>
> besides the DB CLI, you need to configure JMS, using this CLI:
>
> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/configuration
>
> Note, the JMS bits are tied to WF-10.
>
>
> On Mon, May 9, 2016 at 10:19 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> so i'm trying to deploy what is currently on master to wildfly 9(also
>> tried 10) and i'm getting this error:
>>
>> https://gist.github.com/lholmquist/6743191e4c4f225dac7e8e16e86f09fc
>>
>>
>> i've copied the h2 db deployment script to the wildly deployment
>> directory,  manually copied the  auth-server and ag-push war files to the
>> wildlfy deployment directory from their respective target directories,
>>
>> started with "./bin/standalone.sh -c standalone-full.xml -b 0.0.0.0"
>>
>> perhaps i'm missing a step?
>>
>> _______________________________________________
>> 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-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/20160510/abf873e4/attachment.html 

From matzew at apache.org  Tue May 10 09:08:34 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 May 2016 15:08:34 +0200
Subject: [Aerogear-users] [aerogear-dev]  deploy failure for Master
In-Reply-To: <CALD3Fd0xvzuoCWbUEa_S=Yp6CsXVFbzivioJJ2RBOGxCHeOVSQ@mail.gmail.com>
References: <CALD3Fd2ZMbDAosdSFYkFqn4hFJy-TrHj7Y6M3qbFnoH6wWv_bg@mail.gmail.com>
	<CAAg5f2S9SphzfsS60cFAKJRVyWjPAXbL_J_oEefsi4r4x7F24Q@mail.gmail.com>
	<CALD3Fd0xvzuoCWbUEa_S=Yp6CsXVFbzivioJJ2RBOGxCHeOVSQ@mail.gmail.com>
Message-ID: <CAAg5f2RXvLA61Gka9y9+3F4k1gyx3V5QwipzX5HcoBEixupUVw@mail.gmail.com>

yes, I think the two CLI scripts all should go into a common config folder,
and some text needs to be eventually on the guide

On Tue, May 10, 2016 at 2:39 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> ah yes, that did it.
>
> I suppose i should have RTFM,  i usually look at the readme on GH, i'm
> wondering if there should be something there also?
>
> On Tue, May 10, 2016 at 12:11 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi Luke,
>>
>> besides the DB CLI, you need to configure JMS, using this CLI:
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/configuration
>>
>> Note, the JMS bits are tied to WF-10.
>>
>>
>> On Mon, May 9, 2016 at 10:19 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>> so i'm trying to deploy what is currently on master to wildfly 9(also
>>> tried 10) and i'm getting this error:
>>>
>>> https://gist.github.com/lholmquist/6743191e4c4f225dac7e8e16e86f09fc
>>>
>>>
>>> i've copied the h2 db deployment script to the wildly deployment
>>> directory,  manually copied the  auth-server and ag-push war files to the
>>> wildlfy deployment directory from their respective target directories,
>>>
>>> started with "./bin/standalone.sh -c standalone-full.xml -b 0.0.0.0"
>>>
>>> perhaps i'm missing a step?
>>>
>>> _______________________________________________
>>> 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-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>
> _______________________________________________
> 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/20160510/796c19ec/attachment.html 

From asimyuksel at sdu.edu.tr  Tue May 10 09:50:49 2016
From: asimyuksel at sdu.edu.tr (asimsinan)
Date: Tue, 10 May 2016 06:50:49 -0700 (MST)
Subject: [Aerogear-users] Unexpected error running Liquibase: Precondition
	Error
Message-ID: <1462888249676-644.post@n5.nabble.com>

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-Liquibase-Precondition-Error-tp644.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From oliver at dagm8.com  Tue May  3 04:44:41 2016
From: oliver at dagm8.com (oliver)
Date: Tue, 3 May 2016 01:44:41 -0700 (MST)
Subject: [Aerogear-users] Handshake issue when connecting to APNS (from
 OpenShift Online)
In-Reply-To: <CAJ4FD9xMXaj4Qn6PTmPwp8u5wc-QpvFG1nqH613hFHjEfpgCEA@mail.gmail.com>
References: <CAJ4FD9xMXaj4Qn6PTmPwp8u5wc-QpvFG1nqH613hFHjEfpgCEA@mail.gmail.com>
Message-ID: <1462265081425-629.post@n5.nabble.com>

Same issue with aerogear on openshift.



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Handshake-issue-when-connecting-to-APNS-from-OpenShift-Online-tp263p629.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From oliver at dagm8.com  Tue May  3 04:50:22 2016
From: oliver at dagm8.com (oliver)
Date: Tue, 3 May 2016 01:50:22 -0700 (MST)
Subject: [Aerogear-users] Push message don't send
Message-ID: <1462265422234-630.post@n5.nabble.com>

Aerogear don't send message to networks (apn/gcm), server is on openshift
with a non free account.



Also any recomendation for memory and cpu?,

thank you in advance.



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Push-message-don-t-send-tp630.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From matzew at apache.org  Tue May 10 10:12:32 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 May 2016 16:12:32 +0200
Subject: [Aerogear-users] Push message don't send
In-Reply-To: <1462265422234-630.post@n5.nabble.com>
References: <1462265422234-630.post@n5.nabble.com>
Message-ID: <CAAg5f2RNKiMhs23Bnp62yKn5qvH1++iSNhU89NOhsrTX+vZmAA@mail.gmail.com>

no push is going through ?

On Tue, May 3, 2016 at 10:50 AM, oliver <oliver at dagm8.com> wrote:

> Aerogear don't send message to networks (apn/gcm), server is on openshift
> with a non free account.
>
>
>
> Also any recomendation for memory and cpu?,
>
> thank you in advance.
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Push-message-don-t-send-tp630.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
>



-- 
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/20160510/af4e07a9/attachment.html 

From matzew at apache.org  Tue May 10 10:18:19 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 May 2016 16:18:19 +0200
Subject: [Aerogear-users] Unexpected error running Liquibase:
	Precondition Error
In-Reply-To: <1462888249676-644.post@n5.nabble.com>
References: <1462888249676-644.post@n5.nabble.com>
Message-ID: <CAAg5f2Rn=_P3E6qLp9Ar2OVhBxiVOD1Lzchj2T98cRd3WH4yUg@mail.gmail.com>

any more details ? e.g. versions etc ?

On Tue, May 10, 2016 at 3:50 PM, asimsinan <asimyuksel at sdu.edu.tr> wrote:

> 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-Liquibase-Precondition-Error-tp644.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
>



-- 
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/20160510/5cee46e3/attachment.html 

From asimyuksel at sdu.edu.tr  Tue May 10 10:28:23 2016
From: asimyuksel at sdu.edu.tr (asimsinan)
Date: Tue, 10 May 2016 07:28:23 -0700 (MST)
Subject: [Aerogear-users] Unexpected error running Liquibase:
 Precondition Error
In-Reply-To: <CAAg5f2Rn=_P3E6qLp9Ar2OVhBxiVOD1Lzchj2T98cRd3WH4yUg@mail.gmail.com>
References: <1462888249676-644.post@n5.nabble.com>
	<CAAg5f2Rn=_P3E6qLp9Ar2OVhBxiVOD1Lzchj2T98cRd3WH4yUg@mail.gmail.com>
Message-ID: <1462890503571-647.post@n5.nabble.com>

Wildfly: 10.0.0.Final
I am starting wildfly with ./standalone.sh
--server-config=standalone-full.xml
I cloned latest aerogear-unifiedpush-server and installed with maven.
I followed all steps in
https://aerogear.org/docs/unifiedpush/ups_userguide/index/#server-installation.
All was successful.
I am using mysql database. It is running on localhost and the port is 3306.
Mysql connector version is mysql-connector-java-5.1.18. I created all
databases.
liquibase.properties contains the following info

url=jdbc:mysql://localhost:3306/unifiedpush
driver=com.mysql.jdbc.Driver
username=unifiedpush
password=unifiedpush
changeLogFile=/Users/asimsinanyuksel/Desktop/aerogear-unifiedpush-server/migrator/src/main/resources/liquibase/master.xml

I am attaching the error image.
<http://aerogear-users.1116366.n5.nabble.com/file/n647/Ekran_Resmi_2016-05-10_17.png> 



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Unexpected-error-running-Liquibase-Precondition-Error-tp644p647.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From matzew at apache.org  Tue May 10 10:37:16 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 May 2016 16:37:16 +0200
Subject: [Aerogear-users] Unexpected error running Liquibase:
	Precondition Error
In-Reply-To: <1462890503571-647.post@n5.nabble.com>
References: <1462888249676-644.post@n5.nabble.com>
	<CAAg5f2Rn=_P3E6qLp9Ar2OVhBxiVOD1Lzchj2T98cRd3WH4yUg@mail.gmail.com>
	<1462890503571-647.post@n5.nabble.com>
Message-ID: <CAAg5f2Tgs=S+XDFCNCuR=cvQ5u_WZLA4OK_HFW=S7POG_gwxrw@mail.gmail.com>

UPS 1.2.0-x line?

On Tue, May 10, 2016 at 4:28 PM, asimsinan <asimyuksel at sdu.edu.tr> wrote:

> Wildfly: 10.0.0.Final
> I am starting wildfly with ./standalone.sh
> --server-config=standalone-full.xml
> I cloned latest aerogear-unifiedpush-server and installed with maven.
> I followed all steps in
>
> https://aerogear.org/docs/unifiedpush/ups_userguide/index/#server-installation
> .
> All was successful.
> I am using mysql database. It is running on localhost and the port is 3306.
> Mysql connector version is mysql-connector-java-5.1.18. I created all
> databases.
> liquibase.properties contains the following info
>
> url=jdbc:mysql://localhost:3306/unifiedpush
> driver=com.mysql.jdbc.Driver
> username=unifiedpush
> password=unifiedpush
>
> changeLogFile=/Users/asimsinanyuksel/Desktop/aerogear-unifiedpush-server/migrator/src/main/resources/liquibase/master.xml
>
> I am attaching the error image.
> <
> http://aerogear-users.1116366.n5.nabble.com/file/n647/Ekran_Resmi_2016-05-10_17.png
> >
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Unexpected-error-running-Liquibase-Precondition-Error-tp644p647.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
>



-- 
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/20160510/e5fd139a/attachment.html 

From oliver at dagm8.com  Tue May 10 10:41:52 2016
From: oliver at dagm8.com (ODM)
Date: Tue, 10 May 2016 07:41:52 -0700 (MST)
Subject: [Aerogear-users] Push message don't send
In-Reply-To: <CAAg5f2RNKiMhs23Bnp62yKn5qvH1++iSNhU89NOhsrTX+vZmAA@mail.gmail.com>
References: <1462265422234-630.post@n5.nabble.com>
	<CAAg5f2RNKiMhs23Bnp62yKn5qvH1++iSNhU89NOhsrTX+vZmAA@mail.gmail.com>
Message-ID: <1462891312987-649.post@n5.nabble.com>

Hi  Matthias, Nop, everything work again when we restart the openshift
application, this is the second time this happens to us.


I share the files for the day that I think the problem happened.

https://dl.dropboxusercontent.com/u/10103908/server.log.2016-04-29
https://dl.dropboxusercontent.com/u/10103908/server.log.2016-04-30

I hope you can take a look at these.



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Push-message-don-t-send-tp630p649.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From asimyuksel at sdu.edu.tr  Tue May 10 11:11:48 2016
From: asimyuksel at sdu.edu.tr (asimsinan)
Date: Tue, 10 May 2016 08:11:48 -0700 (MST)
Subject: [Aerogear-users] Unexpected error running Liquibase:
 Precondition Error
In-Reply-To: <CAAg5f2Tgs=S+XDFCNCuR=cvQ5u_WZLA4OK_HFW=S7POG_gwxrw@mail.gmail.com>
References: <1462888249676-644.post@n5.nabble.com>
	<CAAg5f2Rn=_P3E6qLp9Ar2OVhBxiVOD1Lzchj2T98cRd3WH4yUg@mail.gmail.com>
	<1462890503571-647.post@n5.nabble.com>
	<CAAg5f2Tgs=S+XDFCNCuR=cvQ5u_WZLA4OK_HFW=S7POG_gwxrw@mail.gmail.com>
Message-ID: <1462893108186-650.post@n5.nabble.com>

Yes UPS 1.2.0-alpha.1



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Unexpected-error-running-Liquibase-Precondition-Error-tp644p650.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From matzew at apache.org  Tue May 10 11:22:20 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 May 2016 17:22:20 +0200
Subject: [Aerogear-users] Unexpected error running Liquibase:
	Precondition Error
In-Reply-To: <1462893108186-650.post@n5.nabble.com>
References: <1462888249676-644.post@n5.nabble.com>
	<CAAg5f2Rn=_P3E6qLp9Ar2OVhBxiVOD1Lzchj2T98cRd3WH4yUg@mail.gmail.com>
	<1462890503571-647.post@n5.nabble.com>
	<CAAg5f2Tgs=S+XDFCNCuR=cvQ5u_WZLA4OK_HFW=S7POG_gwxrw@mail.gmail.com>
	<1462893108186-650.post@n5.nabble.com>
Message-ID: <CAAg5f2TYAY0W6UAQBW4S+wiFiubT0HifYoZ=yn=PrSfkxGAFoQ@mail.gmail.com>

ok, will take a look.

Can you create a JIRA  ?

On Tue, May 10, 2016 at 5:11 PM, asimsinan <asimyuksel at sdu.edu.tr> wrote:

> Yes UPS 1.2.0-alpha.1
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Unexpected-error-running-Liquibase-Precondition-Error-tp644p650.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
>



-- 
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/20160510/3b82f607/attachment.html 

From matzew at apache.org  Tue May 10 11:22:45 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 May 2016 17:22:45 +0200
Subject: [Aerogear-users] Push message don't send
In-Reply-To: <1462891312987-649.post@n5.nabble.com>
References: <1462265422234-630.post@n5.nabble.com>
	<CAAg5f2RNKiMhs23Bnp62yKn5qvH1++iSNhU89NOhsrTX+vZmAA@mail.gmail.com>
	<1462891312987-649.post@n5.nabble.com>
Message-ID: <CAAg5f2TDSqoZu27qoGnt3wnCgv8Z8wJTkCQHUCYf6mRnSMrtQw@mail.gmail.com>

ok, thanks - will take a look later!

On Tue, May 10, 2016 at 4:41 PM, ODM <oliver at dagm8.com> wrote:

> Hi  Matthias, Nop, everything work again when we restart the openshift
> application, this is the second time this happens to us.
>
>
> I share the files for the day that I think the problem happened.
>
> https://dl.dropboxusercontent.com/u/10103908/server.log.2016-04-29
> https://dl.dropboxusercontent.com/u/10103908/server.log.2016-04-30
>
> I hope you can take a look at these.
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Push-message-don-t-send-tp630p649.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
>



-- 
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/20160510/1bee173f/attachment.html 

From asimyuksel at sdu.edu.tr  Tue May 10 12:09:08 2016
From: asimyuksel at sdu.edu.tr (asimsinan)
Date: Tue, 10 May 2016 09:09:08 -0700 (MST)
Subject: [Aerogear-users] Unexpected error running Liquibase:
 Precondition Error
In-Reply-To: <CAAg5f2TYAY0W6UAQBW4S+wiFiubT0HifYoZ=yn=PrSfkxGAFoQ@mail.gmail.com>
References: <1462888249676-644.post@n5.nabble.com>
	<CAAg5f2Rn=_P3E6qLp9Ar2OVhBxiVOD1Lzchj2T98cRd3WH4yUg@mail.gmail.com>
	<1462890503571-647.post@n5.nabble.com>
	<CAAg5f2Tgs=S+XDFCNCuR=cvQ5u_WZLA4OK_HFW=S7POG_gwxrw@mail.gmail.com>
	<1462893108186-650.post@n5.nabble.com>
	<CAAg5f2TYAY0W6UAQBW4S+wiFiubT0HifYoZ=yn=PrSfkxGAFoQ@mail.gmail.com>
Message-ID: <1462896548126-653.post@n5.nabble.com>

When I run mvn clean install dependency:copy-dependencies
-DincludeScope=runtime I get the following error.



liquibase.exception.MigrationFailedException: Migration failed for change
set 1.0.0.Final/initial-mysql.xml::013::generated:
     Reason: 
          master.xml :
liquibase.precondition.core.PrimaryKeyExistsPrecondition at 6e35bc3d : Table
'unifiedpush.?nstallation' doesn't exist

I already have table name Installation. However when I check the table
hibernate file 'Installation.hbm.xml' it has the following

<class name="org.jboss.aerogear.unifiedpush.api.Installation"
table="installation">

Can it be related to a charset problem? The language locale of the OS is
Turkish.





--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Unexpected-error-running-Liquibase-Precondition-Error-tp644p653.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From matzew at apache.org  Tue May 10 12:17:06 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 10 May 2016 18:17:06 +0200
Subject: [Aerogear-users] Unexpected error running Liquibase:
	Precondition Error
In-Reply-To: <1462896548126-653.post@n5.nabble.com>
References: <1462888249676-644.post@n5.nabble.com>
	<CAAg5f2Rn=_P3E6qLp9Ar2OVhBxiVOD1Lzchj2T98cRd3WH4yUg@mail.gmail.com>
	<1462890503571-647.post@n5.nabble.com>
	<CAAg5f2Tgs=S+XDFCNCuR=cvQ5u_WZLA4OK_HFW=S7POG_gwxrw@mail.gmail.com>
	<1462893108186-650.post@n5.nabble.com>
	<CAAg5f2TYAY0W6UAQBW4S+wiFiubT0HifYoZ=yn=PrSfkxGAFoQ@mail.gmail.com>
	<1462896548126-653.post@n5.nabble.com>
Message-ID: <CAAg5f2Q4cqWDMaqVGjrD0RP7Frg1YdB-+=tkG4gibP8Xz+Ro4g@mail.gmail.com>

hrm... really? Isn't it all UTF-8 ? :)

On Tue, May 10, 2016 at 6:09 PM, asimsinan <asimyuksel at sdu.edu.tr> wrote:

> When I run mvn clean install dependency:copy-dependencies
> -DincludeScope=runtime I get the following error.
>
>
>
> liquibase.exception.MigrationFailedException: Migration failed for change
> set 1.0.0.Final/initial-mysql.xml::013::generated:
>      Reason:
>           master.xml :
> liquibase.precondition.core.PrimaryKeyExistsPrecondition at 6e35bc3d : Table
> 'unifiedpush.?nstallation' doesn't exist
>
> I already have table name Installation. However when I check the table
> hibernate file 'Installation.hbm.xml' it has the following
>
> <class name="org.jboss.aerogear.unifiedpush.api.Installation"
> table="installation">
>
> Can it be related to a charset problem? The language locale of the OS is
> Turkish.
>
>
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Unexpected-error-running-Liquibase-Precondition-Error-tp644p653.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
>



-- 
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/20160510/06ee5cd9/attachment.html 

From asimyuksel at sdu.edu.tr  Tue May 10 12:44:11 2016
From: asimyuksel at sdu.edu.tr (asimsinan)
Date: Tue, 10 May 2016 09:44:11 -0700 (MST)
Subject: [Aerogear-users] Unexpected error running Liquibase:
 Precondition Error
In-Reply-To: <CAAg5f2Q4cqWDMaqVGjrD0RP7Frg1YdB-+=tkG4gibP8Xz+Ro4g@mail.gmail.com>
References: <1462888249676-644.post@n5.nabble.com>
	<CAAg5f2Rn=_P3E6qLp9Ar2OVhBxiVOD1Lzchj2T98cRd3WH4yUg@mail.gmail.com>
	<1462890503571-647.post@n5.nabble.com>
	<CAAg5f2Tgs=S+XDFCNCuR=cvQ5u_WZLA4OK_HFW=S7POG_gwxrw@mail.gmail.com>
	<1462893108186-650.post@n5.nabble.com>
	<CAAg5f2TYAY0W6UAQBW4S+wiFiubT0HifYoZ=yn=PrSfkxGAFoQ@mail.gmail.com>
	<1462896548126-653.post@n5.nabble.com>
	<CAAg5f2Q4cqWDMaqVGjrD0RP7Frg1YdB-+=tkG4gibP8Xz+Ro4g@mail.gmail.com>
Message-ID: <1462898651820-655.post@n5.nabble.com>

My guess is it is trying to change i to ? instead of I.



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Unexpected-error-running-Liquibase-Precondition-Error-tp644p655.html
Sent from the aerogear-users mailing list archive at Nabble.com.


From asimyuksel at sdu.edu.tr  Tue May 10 15:01:57 2016
From: asimyuksel at sdu.edu.tr (asimsinan)
Date: Tue, 10 May 2016 12:01:57 -0700 (MST)
Subject: [Aerogear-users] Unexpected error running Liquibase:
 Precondition Error
In-Reply-To: <CAAg5f2Q4cqWDMaqVGjrD0RP7Frg1YdB-+=tkG4gibP8Xz+Ro4g@mail.gmail.com>
References: <1462888249676-644.post@n5.nabble.com>
	<CAAg5f2Rn=_P3E6qLp9Ar2OVhBxiVOD1Lzchj2T98cRd3WH4yUg@mail.gmail.com>
	<1462890503571-647.post@n5.nabble.com>
	<CAAg5f2Tgs=S+XDFCNCuR=cvQ5u_WZLA4OK_HFW=S7POG_gwxrw@mail.gmail.com>
	<1462893108186-650.post@n5.nabble.com>
	<CAAg5f2TYAY0W6UAQBW4S+wiFiubT0HifYoZ=yn=PrSfkxGAFoQ@mail.gmail.com>
	<1462896548126-653.post@n5.nabble.com>
	<CAAg5f2Q4cqWDMaqVGjrD0RP7Frg1YdB-+=tkG4gibP8Xz+Ro4g@mail.gmail.com>
Message-ID: <1462906917270-656.post@n5.nabble.com>

I solved the problem by changing the OS Language to English :) Turkish
language was causing the problem.



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Unexpected-error-running-Liquibase-Precondition-Error-tp644p656.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From laurent.broudoux at gmail.com  Wed May 11 04:45:27 2016
From: laurent.broudoux at gmail.com (Laurent Broudoux)
Date: Wed, 11 May 2016 01:45:27 -0700 (MST)
Subject: [Aerogear-users] Handshake issue when connecting to APNS (from
 OpenShift Online)
In-Reply-To: <1462265081425-629.post@n5.nabble.com>
References: <CAJ4FD9xMXaj4Qn6PTmPwp8u5wc-QpvFG1nqH613hFHjEfpgCEA@mail.gmail.com>
	<1462265081425-629.post@n5.nabble.com>
Message-ID: <1462956327505-657.post@n5.nabble.com>

Hi,
I've checked back with other contacts using AeroGear on OpenShift and they
have encounter same issues on same dates
last weeks : 
   - around 7th - 8th April (depending on timezone),
   - around 27th - 28th April (depending on timezone).

Do you have issues on same dates too ?
Does AeroGear have any connection with this problem or is it purely related
to infrastructure ?
I do not have enough knowledge in certificates and security infrastructure
stuffs to blame Openshift ...
Any clue ?

Thank you,
--
Laurent



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Handshake-issue-when-connecting-to-APNS-from-OpenShift-Online-tp263p657.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From matzew at apache.org  Wed May 11 04:55:31 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 11 May 2016 10:55:31 +0200
Subject: [Aerogear-users] Handshake issue when connecting to APNS (from
 OpenShift Online)
In-Reply-To: <1462956327505-657.post@n5.nabble.com>
References: <CAJ4FD9xMXaj4Qn6PTmPwp8u5wc-QpvFG1nqH613hFHjEfpgCEA@mail.gmail.com>
	<1462265081425-629.post@n5.nabble.com>
	<1462956327505-657.post@n5.nabble.com>
Message-ID: <CAAg5f2REndhM0=G-PCq+oZgX2+G-6iJJfM4uR=9Ti74n0NhrKA@mail.gmail.com>

Hi Laurent,

thanks for the feedback, I'll ask around

-Matthias

On Wed, May 11, 2016 at 10:45 AM, Laurent Broudoux <
laurent.broudoux at gmail.com> wrote:

> Hi,
> I've checked back with other contacts using AeroGear on OpenShift and they
> have encounter same issues on same dates
> last weeks :
>    - around 7th - 8th April (depending on timezone),
>    - around 27th - 28th April (depending on timezone).
>
> Do you have issues on same dates too ?
> Does AeroGear have any connection with this problem or is it purely related
> to infrastructure ?
> I do not have enough knowledge in certificates and security infrastructure
> stuffs to blame Openshift ...
> Any clue ?
>
> Thank you,
> --
> Laurent
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Handshake-issue-when-connecting-to-APNS-from-OpenShift-Online-tp263p657.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
>



-- 
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/20160511/ac72fe6d/attachment-0001.html 

From lholmqui at redhat.com  Thu May 12 14:26:37 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 12 May 2016 14:26:37 -0400
Subject: [Aerogear-users] admin REST client for node
Message-ID: <CALD3Fd1oTjnx8QmgCeUa3t_Lsm_c=rsx2LfH0xysk3fkBBBt_w@mail.gmail.com>

https://www.npmjs.com/package/unifiedpush-admin-client

I remember a little while back someone created an admin client in Java,  so
i decided to start one in node.js

ATM for the 0.1.0 release,  i've only implemented the CRUD for
applications, following these docs
https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/#838429674


The only thing i need to do to get "authenitcated" with keycloak was to
switch direct access grants to on in the "unifiedpush-server-js" client.
it also assumes that you are using the coupled KC/UPS bundle. which i think
is the only way right now.


once they become decoupled, then i can modify the client accordingly.

The tests are currently just mocking what the ups would return.  I would
like to get some integration tests setup, but i'm not to sure how to
automate the "turning on" of the direct access grants.

i could probably use docker for the sever setup

anyway,  here it is  :) and more functionality to come

-Luke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160512/66690676/attachment.html 

From vvalluru at hotmail.com  Fri May 13 11:14:53 2016
From: vvalluru at hotmail.com (vvalluru)
Date: Fri, 13 May 2016 08:14:53 -0700 (MST)
Subject: [Aerogear-users] Message posted through RestAPI does not show up as
	JSON in Android
Message-ID: <1463152493128-661.post@n5.nabble.com>

We are using Unified Push server 1.1.0 final
We created a format for message, which we want to post to our Android and
iOS users. Message has some userData. On iOS, data shows up fine as a proper
JSON, however, for android, the data shows as a string. 

Any Suggestions would be very helpful.
Thanks
Vish

The message submitted is submitted like this:
{ "message": {
"alert" : "Remote service failed. View FAQ's.",
"sound": "default",
"badge": -1,
"user-data": {
"SXM": {
"CATEGORY" : "SERVICE",
"SERVICETYPE": "Remote",
"SRID": "BB4FC7F0-15E9-11E6-9F41-0050569C3256",
"APPCONTENT": "UNKNOWN",
"STATUS": "FAIL",
"STATUSCHANGE_DATETIME": "UNKNOWN",
"URL": "XYZABC.com"}},
"apns": {"action-category": "Service"}},
criteria:
{"alias": ["A337544939901E078A3C7DF1435DFD0B"]}
}


Android receives message like this:
{aerogear-push-id=4d8ea259-ad94-49f0-b470-50fc4bcf3a20, 
SXM={CATEGORY=SERVICE, 
SERVICETYPE=Remote, 
SRID=BB4FC7F0-15E9-11E6-9F41-0050569C3256, 
APPCONTENT=UNKNOWN, 
STATUS=FAIL, 
STATUSCHANGE_DATETIME=UNKNOWN, 
URL=XYZABC.com
}, 
alert=Remote service failed. View FAQ's., 
badge=-1, 
sound=default, 
collapse_key=do_not_collapse
}


If we remove the SXM tag under userData, issue remains the same:

Android receives message like this:
{aerogear-push-id=4d8ea259-ad94-49f0-b470-50fc4bcf3a20, 
CATEGORY=SERVICE, 
SERVICETYPE=Remote, 
SRID=BB4FC7F0-15E9-11E6-9F41-0050569C3256, 
APPCONTENT=UNKNOWN, 
STATUS=FAIL, 
STATUSCHANGE_DATETIME=UNKNOWN, 
URL=XYZABC.com, 
alert=Remote service failed. View FAQ's.,
collapse_key=do_not_collapse
}




--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Message-posted-through-RestAPI-does-not-show-up-as-JSON-in-Android-tp661.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From Philipp.Koetz at mvise.de  Wed May 18 09:10:15 2016
From: Philipp.Koetz at mvise.de (Philipp Koetz, mVISE AG)
Date: Wed, 18 May 2016 13:10:15 +0000
Subject: [Aerogear-users] Unable to resolve realm public key remotely
Message-ID: <1eb3e60edd684b6e8b4dc5d071b029fc@MVI-VWS-MSX01.intranet.local>

Hello,

i've set up the unified push server and run in this stack trace while trying to access /ag-push/

2016-05-18 12:51:24,969 ERROR [io.undertow.request] (default task-8) UT005023: Exception handling request to /ag-push/index.html: java.lang.RuntimeException: Unable to resolve realm public key remotely
        at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        at org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        at org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68) [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]
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method) [rt.jar:1.8.0_72-internal]
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) [rt.jar:1.8.0_72-internal]
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) [rt.jar:1.8.0_72-internal]
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) [rt.jar:1.8.0_72-internal]
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) [rt.jar:1.8.0_72-internal]
        at java.net.Socket.connect(Socket.java:589) [rt.jar:1.8.0_72-internal]
        at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668) [jsse.jar:1.8.0_72-internal]
        at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:524) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57) [httpclient-4.3.6.jar:4.3.6]
        at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:105) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        ... 14 more

SSL setup should be correct, with a self signed cert, till accessing the wildfly start page via https works correctly.
If it helps I can also provide the standalone-full.xml.

I'm using version 1.13 on Wildfly 8.2.1. The error appears on http and https.

Regards,
Philipp Koetz



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160518/2914943d/attachment.html 

From lholmqui at redhat.com  Wed May 18 09:28:23 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Wed, 18 May 2016 09:28:23 -0400
Subject: [Aerogear-users] UPS/Keycloak Decouple status?
Message-ID: <CALD3Fd0wythf2F8U_0vnOe3dVfEQ-TuB64c-b-5iPNcfo0yjuw@mail.gmail.com>

Hey peeps.

while i was doing some work on the node admin client i just cretated, i was
think about this $SUBJECT and saw that the PR is still open,
https://github.com/aerogear/aerogear-unifiedpush-server/pull/677


I know abstractj did some awesome work around this, but i wasn't sure what
the status was.

i see it's been open for a while.


-Luke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160518/864a1a28/attachment-0001.html 

From matzew at apache.org  Wed May 18 09:33:06 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 18 May 2016 15:33:06 +0200
Subject: [Aerogear-users] Unable to resolve realm public key remotely
In-Reply-To: <1eb3e60edd684b6e8b4dc5d071b029fc@MVI-VWS-MSX01.intranet.local>
References: <1eb3e60edd684b6e8b4dc5d071b029fc@MVI-VWS-MSX01.intranet.local>
Message-ID: <CAAg5f2TqNffXjt5Nree3t4fmKuq0XNHuBx4whskW914OB9i00A@mail.gmail.com>

Did you deploy the auth-server.war file?

In our Dockerfiles, we do have example for self-signed certs too (WF-9,
based). Perhaps worth to check it out as well, as a pattern?
https://github.com/aerogear/dockerfiles/tree/1.1.x/wildfly

-M

On Wed, May 18, 2016 at 3:10 PM, Philipp Koetz, mVISE AG <
Philipp.Koetz at mvise.de> wrote:

> Hello,
>
>
>
> i?ve set up the unified push server and run in this stack trace while
> trying to access /ag-push/
>
>
>
> 2016-05-18 12:51:24,969 ERROR [io.undertow.request] (default task-8)
> UT005023: Exception handling request to /ag-push/index.html:
> java.lang.RuntimeException: Unable to resolve realm public key remotely
>
>         at
> org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134)
> [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>         at
> org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83)
> [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>         at
> org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71)
> [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>         at
> org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47)
> [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>         at
> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68)
> [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]
>
> Caused by: java.net.ConnectException: Connection refused
>
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
> [rt.jar:1.8.0_72-internal]
>
>         at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> [rt.jar:1.8.0_72-internal]
>
>         at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> [rt.jar:1.8.0_72-internal]
>
>         at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> [rt.jar:1.8.0_72-internal]
>
>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> [rt.jar:1.8.0_72-internal]
>
>         at java.net.Socket.connect(Socket.java:589)
> [rt.jar:1.8.0_72-internal]
>
>         at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
> [jsse.jar:1.8.0_72-internal]
>
>         at
> org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:524)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:105)
> [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>         ... 14 more
>
>
>
> SSL setup should be correct, with a self signed cert, till accessing the
> wildfly start page via https works correctly.
>
> If it helps I can also provide the standalone-full.xml.
>
>
>
> I?m using version 1.13 on Wildfly 8.2.1. The error appears on http and
> https.
>
>
>
> Regards,
>
> Philipp Koetz
>
>
>
>
>
> _______________________________________________
> 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/20160518/9bbe9094/attachment.html 

From Philipp.Koetz at mvise.de  Wed May 18 09:39:03 2016
From: Philipp.Koetz at mvise.de (Philipp Koetz, mVISE AG)
Date: Wed, 18 May 2016 13:39:03 +0000
Subject: [Aerogear-users] Unable to resolve realm public key remotely
In-Reply-To: <CAAg5f2TqNffXjt5Nree3t4fmKuq0XNHuBx4whskW914OB9i00A@mail.gmail.com>
References: <1eb3e60edd684b6e8b4dc5d071b029fc@MVI-VWS-MSX01.intranet.local>
	<CAAg5f2TqNffXjt5Nree3t4fmKuq0XNHuBx4whskW914OB9i00A@mail.gmail.com>
Message-ID: <e2f2eaae0dca48ddbefc81e84caccdc8@MVI-VWS-MSX01.intranet.local>

Yes, auth-server.war is deployed and running:

2016-05-18 12:50:10,549 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /ag-push
2016-05-18 12:50:10,748 INFO  [org.keycloak.services.resources.KeycloakApplication] (MSC service thread 1-3) Not importing realm aerogear from resource /WEB-INF/ups-realm.json.  It already exists.
2016-05-18 12:50:10,862 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017534: Registered web context: /auth
2016-05-18 12:50:11,013 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "unifiedpush-auth-server.war" (runtime-name : "unifiedpush-auth-server.war")
2016-05-18 12:50:11,013 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "unifiedpush-server-wildfly.war" (runtime-name : "unifiedpush-server-wildfly.war")

When I call auth/ I get a redirect (with the according message) to ag-push/ and then receive ?internatl server error? with the stack trace from the first mail.

I will have a look in the dockerfiles.

Von: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] Im Auftrag von Matthias Wessendorf
Gesendet: Mittwoch, 18. Mai 2016 15:33
An: aerogear-users at lists.jboss.org
Betreff: Re: [Aerogear-users] Unable to resolve realm public key remotely

Did you deploy the auth-server.war file?

In our Dockerfiles, we do have example for self-signed certs too (WF-9, based). Perhaps worth to check it out as well, as a pattern?
https://github.com/aerogear/dockerfiles/tree/1.1.x/wildfly

-M

On Wed, May 18, 2016 at 3:10 PM, Philipp Koetz, mVISE AG <Philipp.Koetz at mvise.de<mailto:Philipp.Koetz at mvise.de>> wrote:
Hello,

i?ve set up the unified push server and run in this stack trace while trying to access /ag-push/

2016-05-18 12:51:24,969 ERROR [io.undertow.request] (default task-8) UT005023: Exception handling request to /ag-push/index.html: java.lang.RuntimeException: Unable to resolve realm public key remotely
        at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        at org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        at org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68) [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]
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method) [rt.jar:1.8.0_72-internal]
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) [rt.jar:1.8.0_72-internal]
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) [rt.jar:1.8.0_72-internal]
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) [rt.jar:1.8.0_72-internal]
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) [rt.jar:1.8.0_72-internal]
        at java.net.Socket.connect(Socket.java:589) [rt.jar:1.8.0_72-internal]
        at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668) [jsse.jar:1.8.0_72-internal]
        at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:524) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57) [httpclient-4.3.6.jar:4.3.6]
        at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:105) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        ... 14 more

SSL setup should be correct, with a self signed cert, till accessing the wildfly start page via https works correctly.
If it helps I can also provide the standalone-full.xml.

I?m using version 1.13 on Wildfly 8.2.1. The error appears on http and https.

Regards,
Philipp Koetz




_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto: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/20160518/484a18da/attachment-0001.html 

From matzew at apache.org  Wed May 18 17:04:11 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 18 May 2016 23:04:11 +0200
Subject: [Aerogear-users] [aerogear-dev] UPS/Keycloak Decouple status?
In-Reply-To: <CALD3Fd0wythf2F8U_0vnOe3dVfEQ-TuB64c-b-5iPNcfo0yjuw@mail.gmail.com>
References: <CALD3Fd0wythf2F8U_0vnOe3dVfEQ-TuB64c-b-5iPNcfo0yjuw@mail.gmail.com>
Message-ID: <CAAg5f2Ro=EcV3qLOJ7g5y7FywpDSpoZXM8X-aYgw_QhuEbY-OQ@mail.gmail.com>

yes, I know it's been open for quite some time :-(

I will try to see if I can update to 1.9.x and than we can merge to master.
It's a good start to get the decouple for a future 1.2.0 release on the
1.2.0.alphp-2

On Wed, May 18, 2016 at 3:28 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> Hey peeps.
>
> while i was doing some work on the node admin client i just cretated, i
> was think about this $SUBJECT and saw that the PR is still open,
> https://github.com/aerogear/aerogear-unifiedpush-server/pull/677
>
>
> I know abstractj did some awesome work around this, but i wasn't sure what
> the status was.
>
> i see it's been open for a while.
>
>
> -Luke
>
>
>
>
> _______________________________________________
> 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/20160518/70b0e83b/attachment.html 

From Philipp.Koetz at mvise.de  Thu May 19 06:12:29 2016
From: Philipp.Koetz at mvise.de (Philipp Koetz, mVISE AG)
Date: Thu, 19 May 2016 10:12:29 +0000
Subject: [Aerogear-users] Unable to resolve realm public key remotely
In-Reply-To: <e2f2eaae0dca48ddbefc81e84caccdc8@MVI-VWS-MSX01.intranet.local>
References: <1eb3e60edd684b6e8b4dc5d071b029fc@MVI-VWS-MSX01.intranet.local>
	<CAAg5f2TqNffXjt5Nree3t4fmKuq0XNHuBx4whskW914OB9i00A@mail.gmail.com>,
	<e2f2eaae0dca48ddbefc81e84caccdc8@MVI-VWS-MSX01.intranet.local>
Message-ID: <1463652745737.41375@mvise.de>

Just to share my "fix" for this problem:

The server is embedded in a bigger infrastructure and is called though vpn tunnel. It looked like that it was not able to determine the realm public key through the tunnel. executing a wget from the vserver itself to /ag-push/index.html solved the problem and the push server can be accessed through the tunnel, even after restart.  Maybe AeroGear Dev Team knows why this was neccessary?

________________________________
Von: aerogear-users-bounces at lists.jboss.org <aerogear-users-bounces at lists.jboss.org> im Auftrag von Philipp Koetz, mVISE AG <Philipp.Koetz at mvise.de>
Gesendet: Mittwoch, 18. Mai 2016 15:39
An: aerogear-users at lists.jboss.org
Betreff: Re: [Aerogear-users] Unable to resolve realm public key remotely

Yes, auth-server.war is deployed and running:

2016-05-18 12:50:10,549 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /ag-push
2016-05-18 12:50:10,748 INFO  [org.keycloak.services.resources.KeycloakApplication] (MSC service thread 1-3) Not importing realm aerogear from resource /WEB-INF/ups-realm.json.  It already exists.
2016-05-18 12:50:10,862 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017534: Registered web context: /auth
2016-05-18 12:50:11,013 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "unifiedpush-auth-server.war" (runtime-name : "unifiedpush-auth-server.war")
2016-05-18 12:50:11,013 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "unifiedpush-server-wildfly.war" (runtime-name : "unifiedpush-server-wildfly.war")

When I call auth/ I get a redirect (with the according message) to ag-push/ and then receive ?internatl server error? with the stack trace from the first mail.

I will have a look in the dockerfiles.

Von: aerogear-users-bounces at lists.jboss.org [mailto:aerogear-users-bounces at lists.jboss.org] Im Auftrag von Matthias Wessendorf
Gesendet: Mittwoch, 18. Mai 2016 15:33
An: aerogear-users at lists.jboss.org
Betreff: Re: [Aerogear-users] Unable to resolve realm public key remotely

Did you deploy the auth-server.war file?

In our Dockerfiles, we do have example for self-signed certs too (WF-9, based). Perhaps worth to check it out as well, as a pattern?
https://github.com/aerogear/dockerfiles/tree/1.1.x/wildfly

-M

On Wed, May 18, 2016 at 3:10 PM, Philipp Koetz, mVISE AG <Philipp.Koetz at mvise.de<mailto:Philipp.Koetz at mvise.de>> wrote:
Hello,

i?ve set up the unified push server and run in this stack trace while trying to access /ag-push/

2016-05-18 12:51:24,969 ERROR [io.undertow.request] (default task-8) UT005023: Exception handling request to /ag-push/index.html: java.lang.RuntimeException: Unable to resolve realm public key remotely
        at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        at org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        at org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68) [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]
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method) [rt.jar:1.8.0_72-internal]
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) [rt.jar:1.8.0_72-internal]
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) [rt.jar:1.8.0_72-internal]
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) [rt.jar:1.8.0_72-internal]
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) [rt.jar:1.8.0_72-internal]
        at java.net.Socket.connect(Socket.java:589) [rt.jar:1.8.0_72-internal]
        at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668) [jsse.jar:1.8.0_72-internal]
        at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:524) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) [httpclient-4.3.6.jar:4.3.6]
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57) [httpclient-4.3.6.jar:4.3.6]
        at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:105) [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
        ... 14 more

SSL setup should be correct, with a self signed cert, till accessing the wildfly start page via https works correctly.
If it helps I can also provide the standalone-full.xml.

I?m using version 1.13 on Wildfly 8.2.1. The error appears on http and https.

Regards,
Philipp Koetz




_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto: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/20160519/ef8fb1f6/attachment-0001.html 

From Philipp.Koetz at mvise.de  Thu May 19 06:25:11 2016
From: Philipp.Koetz at mvise.de (Philipp Koetz, mVISE AG)
Date: Thu, 19 May 2016 10:25:11 +0000
Subject: [Aerogear-users] Documentation Endpoints
Message-ID: <1463653508369.80842@mvise.de>

Hello,


is there some kind of documentation which endpoints (Google, Android, etc.) are called potentially? We would need this to configure our firewall.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160519/9f1ec42e/attachment.html 

From matzew at apache.org  Thu May 19 06:34:15 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 19 May 2016 12:34:15 +0200
Subject: [Aerogear-users] Unable to resolve realm public key remotely
In-Reply-To: <1463652745737.41375@mvise.de>
References: <1eb3e60edd684b6e8b4dc5d071b029fc@MVI-VWS-MSX01.intranet.local>
	<CAAg5f2TqNffXjt5Nree3t4fmKuq0XNHuBx4whskW914OB9i00A@mail.gmail.com>
	<e2f2eaae0dca48ddbefc81e84caccdc8@MVI-VWS-MSX01.intranet.local>
	<1463652745737.41375@mvise.de>
Message-ID: <CAAg5f2R3tJ+M4HQ_eQAxRZf5a_J+dsAYMRfaGjXSHpaNvFdkGQ@mail.gmail.com>

hrm, not atm

perhaps wanna ask at keycloak list?


On Thursday, 19 May 2016, Philipp Koetz, mVISE AG <Philipp.Koetz at mvise.de>
wrote:

> Just to share my "fix" for this problem:
>
> The server is embedded in a bigger infrastructure and is called though vpn
> tunnel. It looked like that it was not able to determine the realm public
> key through the tunnel. executing a wget from the vserver itself to
> /ag-push/index.html solved the problem and the push server can be
> accessed through the tunnel, even after restart.  Maybe AeroGear Dev Team
> knows why this was neccessary?
> ------------------------------
> *Von:* aerogear-users-bounces at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');> <
> aerogear-users-bounces at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>>
> im Auftrag von Philipp Koetz, mVISE AG <Philipp.Koetz at mvise.de
> <javascript:_e(%7B%7D,'cvml','Philipp.Koetz at mvise.de');>>
> *Gesendet:* Mittwoch, 18. Mai 2016 15:39
> *An:* aerogear-users at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users at lists.jboss.org');>
> *Betreff:* Re: [Aerogear-users] Unable to resolve realm public key
> remotely
>
>
> Yes, auth-server.war is deployed and running:
>
>
>
> 2016-05-18 12:50:10,549 INFO  [org.wildfly.extension.undertow] (MSC
> service thread 1-4) JBAS017534: Registered web context: /ag-push
>
> 2016-05-18 12:50:10,748 INFO
> [org.keycloak.services.resources.KeycloakApplication] (MSC service thread
> 1-3) Not importing realm aerogear from resource /WEB-INF/ups-realm.json.
> It already exists.
>
> 2016-05-18 12:50:10,862 INFO  [org.wildfly.extension.undertow] (MSC
> service thread 1-3) JBAS017534: Registered web context: /auth
>
> 2016-05-18 12:50:11,013 INFO  [org.jboss.as.server] (ServerService Thread
> Pool -- 31) JBAS018559: Deployed "unifiedpush-auth-server.war"
> (runtime-name : "unifiedpush-auth-server.war")
>
> 2016-05-18 12:50:11,013 INFO  [org.jboss.as.server] (ServerService Thread
> Pool -- 31) JBAS018559: Deployed "unifiedpush-server-wildfly.war"
> (runtime-name : "unifiedpush-server-wildfly.war")
>
>
>
> When I call auth/ I get a redirect (with the according message) to
> ag-push/ and then receive ?internatl server error? with the stack trace
> from the first mail.
>
>
>
> I will have a look in the dockerfiles.
>
>
>
> *Von:* aerogear-users-bounces at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>
> [mailto:aerogear-users-bounces at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>] *Im
> Auftrag von *Matthias Wessendorf
> *Gesendet:* Mittwoch, 18. Mai 2016 15:33
> *An:* aerogear-users at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','aerogear-users at lists.jboss.org');>
> *Betreff:* Re: [Aerogear-users] Unable to resolve realm public key
> remotely
>
>
>
> Did you deploy the auth-server.war file?
>
>
>
> In our Dockerfiles, we do have example for self-signed certs too (WF-9,
> based). Perhaps worth to check it out as well, as a pattern?
>
> https://github.com/aerogear/dockerfiles/tree/1.1.x/wildfly
>
>
>
> -M
>
>
>
> On Wed, May 18, 2016 at 3:10 PM, Philipp Koetz, mVISE AG <
> Philipp.Koetz at mvise.de
> <javascript:_e(%7B%7D,'cvml','Philipp.Koetz at mvise.de');>> wrote:
>
> Hello,
>
>
>
> i?ve set up the unified push server and run in this stack trace while
> trying to access /ag-push/
>
>
>
> 2016-05-18 12:51:24,969 ERROR [io.undertow.request] (default task-8)
> UT005023: Exception handling request to /ag-push/index.html:
> java.lang.RuntimeException: Unable to resolve realm public key remotely
>
>         at
> org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134)
> [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>         at
> org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83)
> [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>         at
> org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71)
> [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>         at
> org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47)
> [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>         at
> org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68)
> [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]
>
> Caused by: java.net.ConnectException: Connection refused
>
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
> [rt.jar:1.8.0_72-internal]
>
>         at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> [rt.jar:1.8.0_72-internal]
>
>         at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> [rt.jar:1.8.0_72-internal]
>
>         at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> [rt.jar:1.8.0_72-internal]
>
>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> [rt.jar:1.8.0_72-internal]
>
>         at java.net.Socket.connect(Socket.java:589)
> [rt.jar:1.8.0_72-internal]
>
>         at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
> [jsse.jar:1.8.0_72-internal]
>
>         at
> org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:524)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
> [httpclient-4.3.6.jar:4.3.6]
>
>         at
> org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:105)
> [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>         ... 14 more
>
>
>
> SSL setup should be correct, with a self signed cert, till accessing the
> wildfly start page via https works correctly.
>
> If it helps I can also provide the standalone-full.xml.
>
>
>
> I?m using version 1.13 on Wildfly 8.2.1. The error appears on http and
> https.
>
>
>
> Regards,
>
> Philipp Koetz
>
>
>
>
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> <javascript:_e(%7B%7D,'cvml','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
>


-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160519/ced92abf/attachment-0001.html 

From matzew at apache.org  Thu May 19 06:49:00 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 19 May 2016 12:49:00 +0200
Subject: [Aerogear-users] Documentation Endpoints
In-Reply-To: <1463653508369.80842@mvise.de>
References: <1463653508369.80842@mvise.de>
Message-ID: <CAAg5f2T80dkeKiNYkpb9kkbVoTNDX2-MoFO2cTHZbvjDdjfgUQ@mail.gmail.com>

No, not yet :-)

But I think it's a good idea, for these reasons.

HEre is a list of services

Google (GCM)
* https://gcm-http.googleapis.com:443
-> will be https://fcm.googleapis.com:443 at some point, once we are on
Firebase Cloud Messaging

Apple (APNs)
production:
* gateway.push.apple.com:2195
* feedback.push.apple.com:2196
development:
* gateway.sandbox.push.apple.com:2195
* feedback.sandbox.push.apple.com:2196

At some point the proprietary protocol will be replaced with HTTP/2, than
it will be:
* https://api.push.apple.com:443
* https://api.development.push.apple.com:443

Amazon:
* https://api.amazon.com:443

Not really sure for Windows, but I think it's these two:
* MPSN:  https://s.notify.live.net:443
* WNS: https://db3.notify.windows.com


I will send a PR to our website to document these.

Thanks for asking, Philipp!


On Thu, May 19, 2016 at 12:25 PM, Philipp Koetz, mVISE AG <
Philipp.Koetz at mvise.de> wrote:

> Hello,
>
>
> is there some kind of documentation which endpoints (Google, Android,
> etc.) are called potentially? We would need this to configure our
> firewall.
>
> _______________________________________________
> 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/20160519/61203797/attachment.html 

From yves.nicolas at dynamease.com  Thu May 19 07:13:51 2016
From: yves.nicolas at dynamease.com (Yves Nicolas)
Date: Thu, 19 May 2016 13:13:51 +0200
Subject: [Aerogear-users] Unable to resolve realm public key remotely
In-Reply-To: <CAAg5f2R3tJ+M4HQ_eQAxRZf5a_J+dsAYMRfaGjXSHpaNvFdkGQ@mail.gmail.com>
References: <1eb3e60edd684b6e8b4dc5d071b029fc@MVI-VWS-MSX01.intranet.local>
	<CAAg5f2TqNffXjt5Nree3t4fmKuq0XNHuBx4whskW914OB9i00A@mail.gmail.com>
	<e2f2eaae0dca48ddbefc81e84caccdc8@MVI-VWS-MSX01.intranet.local>
	<1463652745737.41375@mvise.de>
	<CAAg5f2R3tJ+M4HQ_eQAxRZf5a_J+dsAYMRfaGjXSHpaNvFdkGQ@mail.gmail.com>
Message-ID: <573D9FEF.9050201@dynamease.com>

This looks very much like the problems I get last week in testing Docker 
file with 1.1.3 final location.
I have not been able to spend more time on it this week but I would 
welcome a better understanding in why this happens in virtual 
environments (tunnel or docker)


Le 19/05/2016 12:34, Matthias Wessendorf a ?crit :
> hrm, not atm
>
> perhaps wanna ask at keycloak list?
>
>
> On Thursday, 19 May 2016, Philipp Koetz, mVISE AG 
> <Philipp.Koetz at mvise.de <mailto:Philipp.Koetz at mvise.de>> wrote:
>
>     Just to share my "fix" for this problem:
>
>     The server is embedded in a bigger infrastructure and is called
>     though vpn tunnel. It looked like that it was not able to
>     determine the realm public key through the tunnel. executing a
>     wget from the vserver itself to /ag-push/index.html solved the
>     problem and the push server can be accessed through the tunnel,
>     even after restart.  Maybe AeroGear Dev Team knows why this was
>     neccessary?
>
>     ------------------------------------------------------------------------
>     *Von:* aerogear-users-bounces at lists.jboss.org
>     <javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>
>     <aerogear-users-bounces at lists.jboss.org
>     <javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>>
>     im Auftrag von Philipp Koetz, mVISE AG <Philipp.Koetz at mvise.de
>     <javascript:_e(%7B%7D,'cvml','Philipp.Koetz at mvise.de');>>
>     *Gesendet:* Mittwoch, 18. Mai 2016 15:39
>     *An:* aerogear-users at lists.jboss.org
>     <javascript:_e(%7B%7D,'cvml','aerogear-users at lists.jboss.org');>
>     *Betreff:* Re: [Aerogear-users] Unable to resolve realm public key
>     remotely
>
>     Yes, auth-server.war is deployed and running:
>
>     2016-05-18 12:50:10,549 INFO [org.wildfly.extension.undertow] (MSC
>     service thread 1-4) JBAS017534: Registered web context: /ag-push
>
>     2016-05-18 12:50:10,748 INFO
>     [org.keycloak.services.resources.KeycloakApplication] (MSC service
>     thread 1-3) Not importing realm aerogear from resource
>     /WEB-INF/ups-realm.json. It already exists.
>
>     2016-05-18 12:50:10,862 INFO [org.wildfly.extension.undertow] (MSC
>     service thread 1-3) JBAS017534: Registered web context: /auth
>
>     2016-05-18 12:50:11,013 INFO [org.jboss.as.server] (ServerService
>     Thread Pool -- 31) JBAS018559: Deployed
>     "unifiedpush-auth-server.war" (runtime-name :
>     "unifiedpush-auth-server.war")
>
>     2016-05-18 12:50:11,013 INFO [org.jboss.as.server] (ServerService
>     Thread Pool -- 31) JBAS018559: Deployed
>     "unifiedpush-server-wildfly.war" (runtime-name :
>     "unifiedpush-server-wildfly.war")
>
>     When I call auth/ I get a redirect (with the according message) to
>     ag-push/ and then receive ?internatl server error? with the stack
>     trace from the first mail.
>
>     I will have a look in the dockerfiles.
>
>     *Von:*aerogear-users-bounces at lists.jboss.org
>     <javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>
>     [mailto:aerogear-users-bounces at lists.jboss.org
>     <javascript:_e(%7B%7D,'cvml','aerogear-users-bounces at lists.jboss.org');>]
>     *Im Auftrag von *Matthias Wessendorf
>     *Gesendet:* Mittwoch, 18. Mai 2016 15:33
>     *An:* aerogear-users at lists.jboss.org
>     <javascript:_e(%7B%7D,'cvml','aerogear-users at lists.jboss.org');>
>     *Betreff:* Re: [Aerogear-users] Unable to resolve realm public key
>     remotely
>
>     Did you deploy the auth-server.war file?
>
>     In our Dockerfiles, we do have example for self-signed certs too
>     (WF-9, based). Perhaps worth to check it out as well, as a pattern?
>
>     https://github.com/aerogear/dockerfiles/tree/1.1.x/wildfly
>
>     -M
>
>     On Wed, May 18, 2016 at 3:10 PM, Philipp Koetz, mVISE AG
>     <Philipp.Koetz at mvise.de
>     <javascript:_e(%7B%7D,'cvml','Philipp.Koetz at mvise.de');>> wrote:
>
>     Hello,
>
>     i?ve set up the unified push server and run in this stack trace
>     while trying to access /ag-push/
>
>     2016-05-18 12:51:24,969 ERROR [io.undertow.request] (default
>     task-8) UT005023: Exception handling request to
>     /ag-push/index.html: java.lang.RuntimeException: Unable to resolve
>     realm public key remotely
>
>     at
>     org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:134)
>     [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>     at
>     org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:83)
>     [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>     at
>     org.keycloak.adapters.PreAuthActionsHandler.preflightCors(PreAuthActionsHandler.java:71)
>     [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>     at
>     org.keycloak.adapters.PreAuthActionsHandler.handleRequest(PreAuthActionsHandler.java:47)
>     [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>     at
>     org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:68)
>     [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]
>
>     Caused by: java.net.ConnectException: Connection refused
>
>     at java.net.PlainSocketImpl.socketConnect(Native Method)
>     [rt.jar:1.8.0_72-internal]
>
>     at
>     java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>     [rt.jar:1.8.0_72-internal]
>
>     at
>     java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
>     [rt.jar:1.8.0_72-internal]
>
>     at
>     java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
>     [rt.jar:1.8.0_72-internal]
>
>     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>     [rt.jar:1.8.0_72-internal]
>
>       at java.net.Socket.connect(Socket.java:589)
>     [rt.jar:1.8.0_72-internal]
>
>     at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
>     [jsse.jar:1.8.0_72-internal]
>
>     at
>     org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:524)
>     [httpclient-4.3.6.jar:4.3.6]
>
>     at
>     org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403)
>     [httpclient-4.3.6.jar:4.3.6]
>
>     at
>     org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
>     [httpclient-4.3.6.jar:4.3.6]
>
>     at
>     org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
>     [httpclient-4.3.6.jar:4.3.6]
>
>     at
>     org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
>     [httpclient-4.3.6.jar:4.3.6]
>
>     at
>     org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
>     [httpclient-4.3.6.jar:4.3.6]
>
>     at
>     org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
>     [httpclient-4.3.6.jar:4.3.6]
>
>     at
>     org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
>     [httpclient-4.3.6.jar:4.3.6]
>
>     at
>     org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
>     [httpclient-4.3.6.jar:4.3.6]
>
>     at
>     org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
>     [httpclient-4.3.6.jar:4.3.6]
>
>     at
>     org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
>     [httpclient-4.3.6.jar:4.3.6]
>
>     at
>     org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:105)
>     [keycloak-adapter-core-1.3.1.Final.jar:1.3.1.Final]
>
>     ... 14 more
>
>     SSL setup should be correct, with a self signed cert, till
>     accessing the wildfly start page via https works correctly.
>
>     If it helps I can also provide the standalone-full.xml.
>
>     I?m using version 1.13 on Wildfly 8.2.1. The error appears on http
>     and https.
>
>     Regards,
>
>     Philipp Koetz
>
>
>     _______________________________________________
>     Aerogear-users mailing list
>     Aerogear-users at lists.jboss.org
>     <javascript:_e(%7B%7D,'cvml','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
>
>
>
> -- 
> Sent from Gmail Mobile
>
>
> _______________________________________________
> 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/20160519/79f30b00/attachment-0001.html 

From Philipp.Koetz at mvise.de  Thu May 19 07:56:36 2016
From: Philipp.Koetz at mvise.de (Philipp Koetz, mVISE AG)
Date: Thu, 19 May 2016 11:56:36 +0000
Subject: [Aerogear-users] Documentation Endpoints
In-Reply-To: <CAAg5f2T80dkeKiNYkpb9kkbVoTNDX2-MoFO2cTHZbvjDdjfgUQ@mail.gmail.com>
References: <1463653508369.80842@mvise.de>,
	<CAAg5f2T80dkeKiNYkpb9kkbVoTNDX2-MoFO2cTHZbvjDdjfgUQ@mail.gmail.com>
Message-ID: <1463658992730.75714@mvise.de>

Thanks for your fast reply! This saves a lot of time :)

Is there also a Deeplink for registering devices? I'm looking currently in the documentation for the clients and just found [server address]/ag-push.

As i see it would not possible to login if /auth is not accessible but /ag-push. If i'am right it should be save to expose /ag-push directly to the internet. Can you confirm this?

________________________________
Von: aerogear-users-bounces at lists.jboss.org <aerogear-users-bounces at lists.jboss.org> im Auftrag von Matthias Wessendorf <matzew at apache.org>
Gesendet: Donnerstag, 19. Mai 2016 12:49
An: aerogear-users at lists.jboss.org
Betreff: Re: [Aerogear-users] Documentation Endpoints

No, not yet :-)

But I think it's a good idea, for these reasons.

HEre is a list of services

Google (GCM)
* https://gcm-http.googleapis.com:443
-> will be https://fcm.googleapis.com:443 at some point, once we are on Firebase Cloud Messaging

Apple (APNs)
production:
* gateway.push.apple.com:2195<http://gateway.push.apple.com:2195>
* feedback.push.apple.com:2196<http://feedback.push.apple.com:2196>
development:
* gateway.sandbox.push.apple.com:2195<http://gateway.sandbox.push.apple.com:2195>
* feedback.sandbox.push.apple.com:2196<http://feedback.sandbox.push.apple.com:2196>

At some point the proprietary protocol will be replaced with HTTP/2, than it will be:
* https://api.push.apple.com:443
* https://api.development.push.apple.com:443

Amazon:
* https://api.amazon.com:443

Not really sure for Windows, but I think it's these two:
* MPSN:  https://s.notify.live.net:443
* WNS: https://db3.notify.windows.com


I will send a PR to our website to document these.

Thanks for asking, Philipp!


On Thu, May 19, 2016 at 12:25 PM, Philipp Koetz, mVISE AG <Philipp.Koetz at mvise.de<mailto:Philipp.Koetz at mvise.de>> wrote:

Hello,


is there some kind of documentation which endpoints (Google, Android, etc.) are called potentially? We would need this to configure our firewall.

_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto: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/20160519/8239eade/attachment.html 

From matzew at apache.org  Thu May 19 08:24:59 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 19 May 2016 14:24:59 +0200
Subject: [Aerogear-users] Documentation Endpoints
In-Reply-To: <1463658992730.75714@mvise.de>
References: <1463653508369.80842@mvise.de>
	<CAAg5f2T80dkeKiNYkpb9kkbVoTNDX2-MoFO2cTHZbvjDdjfgUQ@mail.gmail.com>
	<1463658992730.75714@mvise.de>
Message-ID: <CAAg5f2T7QpnQG25EGEq8t3eVPbYxhBsKQhMiaD+VgP24os0S_Q@mail.gmail.com>

See here:
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/servers/ups-wildfly/src/main/webapp/WEB-INF/web.xml#L24-L25

these are the enpoints the devices, and the sender libs (e.g. node/java)
talk to. they are not protected by Keycloak, they use HHTP_Basic

I'd say those are enoguh, if the Admin-UI should not be exposed

-M



On Thu, May 19, 2016 at 1:56 PM, Philipp Koetz, mVISE AG <
Philipp.Koetz at mvise.de> wrote:

> Thanks for your fast reply! This saves a lot of time :)
>
> Is there also a Deeplink for registering devices? I'm looking currently in
> the documentation for the clients and just found [server address]/ag-push.
>
> As i see it would not possible to login if /auth is not accessible but
> /ag-push. If i'am right it should be save to expose /ag-push directly to
> the internet. Can you confirm this?
> ------------------------------
> *Von:* aerogear-users-bounces at lists.jboss.org <
> aerogear-users-bounces at lists.jboss.org> im Auftrag von Matthias
> Wessendorf <matzew at apache.org>
> *Gesendet:* Donnerstag, 19. Mai 2016 12:49
> *An:* aerogear-users at lists.jboss.org
> *Betreff:* Re: [Aerogear-users] Documentation Endpoints
>
> No, not yet :-)
>
> But I think it's a good idea, for these reasons.
>
> HEre is a list of services
>
> Google (GCM)
> * https://gcm-http.googleapis.com:443
> -> will be https://fcm.googleapis.com:443 at some point, once we are on
> Firebase Cloud Messaging
>
> Apple (APNs)
> production:
> * gateway.push.apple.com:2195
> * feedback.push.apple.com:2196
> development:
> * gateway.sandbox.push.apple.com:2195
> * feedback.sandbox.push.apple.com:2196
>
> At some point the proprietary protocol will be replaced with HTTP/2, than
> it will be:
> * https://api.push.apple.com:443
> * https://api.development.push.apple.com:443
>
> Amazon:
> * https://api.amazon.com:443
>
> Not really sure for Windows, but I think it's these two:
> * MPSN:  https://s.notify.live.net:443
> * WNS: https://db3.notify.windows.com
>
>
> I will send a PR to our website to document these.
>
> Thanks for asking, Philipp!
>
>
> On Thu, May 19, 2016 at 12:25 PM, Philipp Koetz, mVISE AG <
> Philipp.Koetz at mvise.de> wrote:
>
>> Hello,
>>
>>
>> is there some kind of documentation which endpoints (Google, Android,
>> etc.) are called potentially? We would need this to configure our
>> firewall.
>>
>> _______________________________________________
>> 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
>
>


-- 
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/20160519/6b55de20/attachment.html 

From lholmqui at redhat.com  Thu May 19 15:21:04 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 19 May 2016 15:21:04 -0400
Subject: [Aerogear-users] Variant Updates return 200 but docs say 204
Message-ID: <CALD3Fd18QPKjnXOzSrGbRMZXSwGhB4dDB-gP_TA7_drg0Dpr9w@mail.gmail.com>

The variant update endpoint returns a 200 with the updated content, but the
docs says it should return a 204 with no Content

i've create a JIRA for it,  https://issues.jboss.org/browse/AGPUSH-1635


I think PUT's are suppose to be 204's, but there might be things relying on
the fact that the update returns data,

here is a link to the AndroidVariants update endpoint,
https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/applications/AndroidVariantEndpoint.java#L142
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160519/47640211/attachment-0001.html 

From matzew at apache.org  Thu May 19 22:45:52 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 20 May 2016 04:45:52 +0200
Subject: [Aerogear-users] Documentation Endpoints
In-Reply-To: <CAAg5f2T7QpnQG25EGEq8t3eVPbYxhBsKQhMiaD+VgP24os0S_Q@mail.gmail.com>
References: <1463653508369.80842@mvise.de>
	<CAAg5f2T80dkeKiNYkpb9kkbVoTNDX2-MoFO2cTHZbvjDdjfgUQ@mail.gmail.com>
	<1463658992730.75714@mvise.de>
	<CAAg5f2T7QpnQG25EGEq8t3eVPbYxhBsKQhMiaD+VgP24os0S_Q@mail.gmail.com>
Message-ID: <CAAg5f2Q+2N8LvvS9MqrrzS_WpAOj64K6NayM=sVS=B24CWdU8Q@mail.gmail.com>

ah, btw. ...

perhaps this is something you also might be interested in:
https://github.com/matzew/ups-proxy

haven't tried that recently... but it used to work :)

On Thu, May 19, 2016 at 2:24 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> See here:
>
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/servers/ups-wildfly/src/main/webapp/WEB-INF/web.xml#L24-L25
>
> these are the enpoints the devices, and the sender libs (e.g. node/java)
> talk to. they are not protected by Keycloak, they use HHTP_Basic
>
> I'd say those are enoguh, if the Admin-UI should not be exposed
>
> -M
>
>
>
> On Thu, May 19, 2016 at 1:56 PM, Philipp Koetz, mVISE AG <
> Philipp.Koetz at mvise.de> wrote:
>
>> Thanks for your fast reply! This saves a lot of time :)
>>
>> Is there also a Deeplink for registering devices? I'm looking currently
>> in the documentation for the clients and just found [server
>> address]/ag-push.
>>
>> As i see it would not possible to login if /auth is not accessible but
>> /ag-push. If i'am right it should be save to expose /ag-push directly to
>> the internet. Can you confirm this?
>> ------------------------------
>> *Von:* aerogear-users-bounces at lists.jboss.org <
>> aerogear-users-bounces at lists.jboss.org> im Auftrag von Matthias
>> Wessendorf <matzew at apache.org>
>> *Gesendet:* Donnerstag, 19. Mai 2016 12:49
>> *An:* aerogear-users at lists.jboss.org
>> *Betreff:* Re: [Aerogear-users] Documentation Endpoints
>>
>> No, not yet :-)
>>
>> But I think it's a good idea, for these reasons.
>>
>> HEre is a list of services
>>
>> Google (GCM)
>> * https://gcm-http.googleapis.com:443
>> -> will be https://fcm.googleapis.com:443 at some point, once we are on
>> Firebase Cloud Messaging
>>
>> Apple (APNs)
>> production:
>> * gateway.push.apple.com:2195
>> * feedback.push.apple.com:2196
>> development:
>> * gateway.sandbox.push.apple.com:2195
>> * feedback.sandbox.push.apple.com:2196
>>
>> At some point the proprietary protocol will be replaced with HTTP/2, than
>> it will be:
>> * https://api.push.apple.com:443
>> * https://api.development.push.apple.com:443
>>
>> Amazon:
>> * https://api.amazon.com:443
>>
>> Not really sure for Windows, but I think it's these two:
>> * MPSN:  https://s.notify.live.net:443
>> * WNS: https://db3.notify.windows.com
>>
>>
>> I will send a PR to our website to document these.
>>
>> Thanks for asking, Philipp!
>>
>>
>> On Thu, May 19, 2016 at 12:25 PM, Philipp Koetz, mVISE AG <
>> Philipp.Koetz at mvise.de> wrote:
>>
>>> Hello,
>>>
>>>
>>> is there some kind of documentation which endpoints (Google, Android,
>>> etc.) are called potentially? We would need this to configure our
>>> firewall.
>>>
>>> _______________________________________________
>>> 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
>>
>>
>
>
> --
> 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/20160520/e35f50e9/attachment.html 

From kurrent93 at gmail.com  Fri May 20 15:11:12 2016
From: kurrent93 at gmail.com (Anton)
Date: Fri, 20 May 2016 21:11:12 +0200
Subject: [Aerogear-users] USP with external Keycloak
Message-ID: <CAD44pJC36_hWJcYEGkJxNBbDVqW6wcVpmctix_SG1fgi82bYFQ@mail.gmail.com>

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160520/91b66bb3/attachment.html 

From lholmqui at redhat.com  Fri May 20 15:39:17 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Fri, 20 May 2016 15:39:17 -0400
Subject: [Aerogear-users] USP with external Keycloak
In-Reply-To: <CAD44pJC36_hWJcYEGkJxNBbDVqW6wcVpmctix_SG1fgi82bYFQ@mail.gmail.com>
References: <CAD44pJC36_hWJcYEGkJxNBbDVqW6wcVpmctix_SG1fgi82bYFQ@mail.gmail.com>
Message-ID: <CALD3Fd1q-w=EGiUV_J0gLeryfTL4qYGNrHvj_TNbOCJa_efJ9Q@mail.gmail.com>

you may be interested in this PR
https://github.com/aerogear/aerogear-unifiedpush-server/pull/677



On Fri, May 20, 2016 at 3:11 PM, Anton <kurrent93 at gmail.com> wrote:

> 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
>
>
>
> _______________________________________________
> 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/20160520/de15eed5/attachment.html 

From matzew at apache.org  Fri May 20 15:45:42 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Fri, 20 May 2016 21:45:42 +0200
Subject: [Aerogear-users] USP with external Keycloak
In-Reply-To: <CALD3Fd1q-w=EGiUV_J0gLeryfTL4qYGNrHvj_TNbOCJa_efJ9Q@mail.gmail.com>
References: <CAD44pJC36_hWJcYEGkJxNBbDVqW6wcVpmctix_SG1fgi82bYFQ@mail.gmail.com>
	<CALD3Fd1q-w=EGiUV_J0gLeryfTL4qYGNrHvj_TNbOCJa_efJ9Q@mail.gmail.com>
Message-ID: <CAAg5f2Tw25M9VVsF0r_amgksBb__13ie95sEF7R0+7h8wHKuaw@mail.gmail.com>

That's right.

It's even possible today, but there are some nasty manual steps involved.

I tried a few month ago with the Keycloak server, from the WildFly-Swarm
project:
https://github.com/wildfly-swarm/wildfly-swarm-keycloak

Some of the changes in that PR (e.g. the location of the JS files, URLs
etc) need to be corrected.
The UPS war needs also be updated (E.g. URI), so that it works.

It's time to revisit the PR and see if we can also get a "out of the box"
bundle (e.g. via KC subsystem or even their standalone distribution
(containing WildFly).

-Matthias


On Fri, May 20, 2016 at 9:39 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> you may be interested in this PR
> https://github.com/aerogear/aerogear-unifiedpush-server/pull/677
>
>
>
> On Fri, May 20, 2016 at 3:11 PM, Anton <kurrent93 at gmail.com> wrote:
>
>> 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
>>
>>
>>
>> _______________________________________________
>> 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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160520/885027bc/attachment-0001.html 

From matzew at apache.org  Fri May 20 19:04:45 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Sat, 21 May 2016 01:04:45 +0200
Subject: [Aerogear-users] USP with external Keycloak
In-Reply-To: <CAAg5f2Tw25M9VVsF0r_amgksBb__13ie95sEF7R0+7h8wHKuaw@mail.gmail.com>
References: <CAD44pJC36_hWJcYEGkJxNBbDVqW6wcVpmctix_SG1fgi82bYFQ@mail.gmail.com>
	<CALD3Fd1q-w=EGiUV_J0gLeryfTL4qYGNrHvj_TNbOCJa_efJ9Q@mail.gmail.com>
	<CAAg5f2Tw25M9VVsF0r_amgksBb__13ie95sEF7R0+7h8wHKuaw@mail.gmail.com>
Message-ID: <CAAg5f2TgR27YrqsqYWs2Ho6tq6HSen2-HuQb8_8s28At7pSc8g@mail.gmail.com>

On Fri, May 20, 2016 at 9:45 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> That's right.
>
> It's even possible today, but there are some nasty manual steps involved.
>
> I tried a few month ago with the Keycloak server, from the WildFly-Swarm
> project:
> https://github.com/wildfly-swarm/wildfly-swarm-keycloak
>
> Some of the changes in that PR (e.g. the location of the JS files, URLs
> etc) need to be corrected.
> The UPS war needs also be updated (E.g. URI), so that it works.
>

meaning, if you do something like run both WARs on different servers, the
changes from the PR need to be applied to your own work :)



>
> It's time to revisit the PR and see if we can also get a "out of the box"
> bundle (e.g. via KC subsystem or even their standalone distribution
> (containing WildFly).
>
> -Matthias
>
>
> On Fri, May 20, 2016 at 9:39 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> you may be interested in this PR
>> https://github.com/aerogear/aerogear-unifiedpush-server/pull/677
>>
>>
>>
>> On Fri, May 20, 2016 at 3:11 PM, Anton <kurrent93 at gmail.com> wrote:
>>
>>> 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
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/
> twitter: http://twitter.com/mwessendorf
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160521/a96fba41/attachment.html 

From ashishkumarpandita at gmail.com  Mon May 23 08:34:21 2016
From: ashishkumarpandita at gmail.com (ashish)
Date: Mon, 23 May 2016 05:34:21 -0700 (MST)
Subject: [Aerogear-users] KeychainWrapper
Message-ID: <1464006861010-680.post@n5.nabble.com>

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.html

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.

From ashishkumarpandita at gmail.com  Mon May 23 12:26:41 2016
From: ashishkumarpandita at gmail.com (ashish)
Date: Mon, 23 May 2016 09:26:41 -0700 (MST)
Subject: [Aerogear-users] KeychainWrapper
In-Reply-To: <1464006861010-680.post@n5.nabble.com>
References: <1464006861010-680.post@n5.nabble.com>
Message-ID: <1464020801437-681.post@n5.nabble.com>

Thanks I got it accountId can be set from client and can be any string.  It
took some time to find bits and pieces but works fine.




--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/KeychainWrapper-tp680p681.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From ashishkumarpandita at gmail.com  Mon May 23 12:33:48 2016
From: ashishkumarpandita at gmail.com (ashish)
Date: Mon, 23 May 2016 09:33:48 -0700 (MST)
Subject: [Aerogear-users] Not able to receive OpenIDClaim and
 accesstoken from redirecturi in iOS app
In-Reply-To: <1462521672470-639.post@n5.nabble.com>
References: <1462521672470-639.post@n5.nabble.com>
Message-ID: <1464021228799-682.post@n5.nabble.com>

It is a bug raised here 
https://issues.jboss.org/browse/AGIOS-489



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Not-able-to-receive-OpenIDClaim-and-accesstoken-from-redirecturi-in-iOS-app-tp639p682.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From aliok at apache.org  Thu May 26 02:14:21 2016
From: aliok at apache.org (aliok)
Date: Wed, 25 May 2016 23:14:21 -0700 (MST)
Subject: [Aerogear-users] Unexpected error running Liquibase:
 Precondition Error
In-Reply-To: <1462906917270-656.post@n5.nabble.com>
References: <1462888249676-644.post@n5.nabble.com>
	<CAAg5f2Rn=_P3E6qLp9Ar2OVhBxiVOD1Lzchj2T98cRd3WH4yUg@mail.gmail.com>
	<1462890503571-647.post@n5.nabble.com>
	<CAAg5f2Tgs=S+XDFCNCuR=cvQ5u_WZLA4OK_HFW=S7POG_gwxrw@mail.gmail.com>
	<1462893108186-650.post@n5.nabble.com>
	<CAAg5f2TYAY0W6UAQBW4S+wiFiubT0HifYoZ=yn=PrSfkxGAFoQ@mail.gmail.com>
	<1462896548126-653.post@n5.nabble.com>
	<CAAg5f2Q4cqWDMaqVGjrD0RP7Frg1YdB-+=tkG4gibP8Xz+Ro4g@mail.gmail.com>
	<1462906917270-656.post@n5.nabble.com>
Message-ID: <1464243261765-683.post@n5.nabble.com>

This is a Liquibase bug. Created https://liquibase.jira.com/browse/CORE-2772
Perhaps it only happens on OSX. I couldn't reproduce it on Linux (through
Docker).

Noted it down at https://issues.jboss.org/browse/AGPUSH-1623



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Unexpected-error-running-Liquibase-Precondition-Error-tp644p683.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From matzew at apache.org  Thu May 26 03:59:13 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 26 May 2016 09:59:13 +0200
Subject: [Aerogear-users] Unexpected error running Liquibase:
	Precondition Error
In-Reply-To: <1464243261765-683.post@n5.nabble.com>
References: <1462888249676-644.post@n5.nabble.com>
	<CAAg5f2Rn=_P3E6qLp9Ar2OVhBxiVOD1Lzchj2T98cRd3WH4yUg@mail.gmail.com>
	<1462890503571-647.post@n5.nabble.com>
	<CAAg5f2Tgs=S+XDFCNCuR=cvQ5u_WZLA4OK_HFW=S7POG_gwxrw@mail.gmail.com>
	<1462893108186-650.post@n5.nabble.com>
	<CAAg5f2TYAY0W6UAQBW4S+wiFiubT0HifYoZ=yn=PrSfkxGAFoQ@mail.gmail.com>
	<1462896548126-653.post@n5.nabble.com>
	<CAAg5f2Q4cqWDMaqVGjrD0RP7Frg1YdB-+=tkG4gibP8Xz+Ro4g@mail.gmail.com>
	<1462906917270-656.post@n5.nabble.com>
	<1464243261765-683.post@n5.nabble.com>
Message-ID: <CAAg5f2S9==9Y5RF7MJL86jW1crOy1ZZ9Z=BbAenekxkU3fNq1Q@mail.gmail.com>

thanks Ali!

On Thursday, 26 May 2016, aliok <aliok at apache.org> wrote:

> This is a Liquibase bug. Created
> https://liquibase.jira.com/browse/CORE-2772
> Perhaps it only happens on OSX. I couldn't reproduce it on Linux (through
> Docker).
>
> Noted it down at https://issues.jboss.org/browse/AGPUSH-1623
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Unexpected-error-running-Liquibase-Precondition-Error-tp644p683.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org <javascript:;>
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>


-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160526/33e95b5c/attachment.html 

From Philipp.Koetz at mvise.de  Fri May 27 07:25:30 2016
From: Philipp.Koetz at mvise.de (Philipp Koetz, mVISE AG)
Date: Fri, 27 May 2016 11:25:30 +0000
Subject: [Aerogear-users] Device registration - Method not allowed
Message-ID: <1464348325054.94450@mvise.de>

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]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160527/3cf48ec6/attachment-0001.html 

From supittma at redhat.com  Fri May 27 08:08:58 2016
From: supittma at redhat.com (Summers Pittman)
Date: Fri, 27 May 2016 08:08:58 -0400
Subject: [Aerogear-users] Device registration - Method not allowed
In-Reply-To: <1464348325054.94450@mvise.de>
References: <1464348325054.94450@mvise.de>
Message-ID: <CAEQz2CsNO+s12KK67h6V8k1uuc9JopKVER71vRNR8ZLLXTb+=g@mail.gmail.com>

Have you registered an Android variant?  This stack trace implies that you
are trying to hit the android registration endpoint but you don't have the
right credentials (which would be the variant ID and secret)

On Fri, May 27, 2016 at 7:25 AM, Philipp Koetz, mVISE AG <
Philipp.Koetz at mvise.de> wrote:

> 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]
>
>
>
> _______________________________________________
> 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/20160527/8f4e36c7/attachment-0001.html 

From lholmqui at redhat.com  Fri May 27 15:56:16 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Fri, 27 May 2016 15:56:16 -0400
Subject: [Aerogear-users] UPS Device Registration Endpoints
Message-ID: <CALD3Fd3EomTCmo4Mte7x7ohkPkAPH+fFz3NWiXFOWbVZp3kOMA@mail.gmail.com>

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160527/1e32660b/attachment.html 

From scm.blanc at gmail.com  Fri May 27 16:10:24 2016
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Fri, 27 May 2016 22:10:24 +0200
Subject: [Aerogear-users] UPS Device Registration Endpoints
In-Reply-To: <CALD3Fd3EomTCmo4Mte7x7ohkPkAPH+fFz3NWiXFOWbVZp3kOMA@mail.gmail.com>
References: <CALD3Fd3EomTCmo4Mte7x7ohkPkAPH+fFz3NWiXFOWbVZp3kOMA@mail.gmail.com>
Message-ID: <F087E56F-5BCC-43BB-B3DD-5D1E95A06379@gmail.com>



Envoy? de mon iPhone

> Le 27 mai 2016 ? 21:56, Luke Holmquist <lholmqui at redhat.com> a ?crit :
> 
> 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
Let's wait for Matzew to confirm but I think you can ignore it. Looks like a left over from our first analytics implementation , we use now a separate endpoint (the PUT) and pass this ID as a path parameter.
We probably need to clean up the javadoc
> 
> 
> 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.
Make sense , I like that 
> 
> 
> -Luke
> _______________________________________________
> 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/20160527/4bb13f8f/attachment.html 

From matzew at apache.org  Sat May 28 00:50:43 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Sat, 28 May 2016 06:50:43 +0200
Subject: [Aerogear-users] UPS Device Registration Endpoints
In-Reply-To: <F087E56F-5BCC-43BB-B3DD-5D1E95A06379@gmail.com>
References: <CALD3Fd3EomTCmo4Mte7x7ohkPkAPH+fFz3NWiXFOWbVZp3kOMA@mail.gmail.com>
	<F087E56F-5BCC-43BB-B3DD-5D1E95A06379@gmail.com>
Message-ID: <CAAg5f2TteiGiE680MYGy7P7=kZfpdYAKcJLm-_JMrwQpAaFoow@mail.gmail.com>

On Fri, May 27, 2016 at 10:10 PM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

>
>
> Envoy? de mon iPhone
>
> Le 27 mai 2016 ? 21:56, Luke Holmquist <lholmqui at redhat.com> a ?crit :
>
> 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
>
> Let's wait for Matzew to confirm but I think you can ignore it. Looks like
> a left over from our first analytics implementation , we use now a separate
> endpoint (the PUT) and pass this ID as a path parameter.
> We probably need to clean up the javadoc
>

correct, doc error.

the thing is only relevant here:
https://github.com/aerogear/aerogear-unifiedpush-server/blob/252c3a979cf05b69f061f7ffa6d3dcc8826c7b51/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/installations/InstallationRegistrationEndpoint.java#L203



>
>
>
> 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.
>
> even if they were KC managed, they would be different (E.g. just
bearer-only), since there is no relationship to the actual mgmt of the
server.

+1 on separating these two things

-M



>   and they could also be used on a IOT device or something that runs node
> that has webpush/simplePush or some new crazy protocol.
>
> Make sense , I like that
>
>
>
> -Luke
>
> _______________________________________________
> 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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160528/5c140d6c/attachment.html 

From lholmqui at redhat.com  Tue May 31 15:07:19 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Tue, 31 May 2016 15:07:19 -0400
Subject: [Aerogear-users] [aerogear-dev] UPS Device Registration
	Endpoints
In-Reply-To: <CAAg5f2TteiGiE680MYGy7P7=kZfpdYAKcJLm-_JMrwQpAaFoow@mail.gmail.com>
References: <CALD3Fd3EomTCmo4Mte7x7ohkPkAPH+fFz3NWiXFOWbVZp3kOMA@mail.gmail.com>
	<F087E56F-5BCC-43BB-B3DD-5D1E95A06379@gmail.com>
	<CAAg5f2TteiGiE680MYGy7P7=kZfpdYAKcJLm-_JMrwQpAaFoow@mail.gmail.com>
Message-ID: <CALD3Fd3hN1BLFic0vFZOtVocEM11oRkPfJ21FRnDZ9b1gb-Egg@mail.gmail.com>

Thanks for the info guys.

Also i just released the 0.1.0 version of this
https://www.npmjs.com/package/unifiedpush-registration-client

a client for doing device registration.

Currently implemented is register and unregister.  i'm working on getting
the "importer" working for the next release.



On Sat, May 28, 2016 at 12:50 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

>
>
> On Fri, May 27, 2016 at 10:10 PM, Sebastien Blanc <scm.blanc at gmail.com>
> wrote:
>
>>
>>
>> Envoy? de mon iPhone
>>
>> Le 27 mai 2016 ? 21:56, Luke Holmquist <lholmqui at redhat.com> a ?crit :
>>
>> 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
>>
>> Let's wait for Matzew to confirm but I think you can ignore it. Looks
>> like a left over from our first analytics implementation , we use now a
>> separate endpoint (the PUT) and pass this ID as a path parameter.
>> We probably need to clean up the javadoc
>>
>
> correct, doc error.
>
> the thing is only relevant here:
>
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/252c3a979cf05b69f061f7ffa6d3dcc8826c7b51/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/installations/InstallationRegistrationEndpoint.java#L203
>
>
>
>>
>>
>>
>> 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.
>>
>> even if they were KC managed, they would be different (E.g. just
> bearer-only), since there is no relationship to the actual mgmt of the
> server.
>
> +1 on separating these two things
>
> -M
>
>
>
>>   and they could also be used on a IOT device or something that runs node
>> that has webpush/simplePush or some new crazy protocol.
>>
>> Make sense , I like that
>>
>>
>>
>> -Luke
>>
>> _______________________________________________
>> 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/
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160531/d925fa64/attachment-0001.html