[Aerogear-users] Documentation Endpoints

[Matthias Wessendorf]

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