I have read the Aerogear's REST API docs, but I could not find a way to
get all the categories a device token subscribes.
Will I have to query the MySQL database directly to get that information?
Cenin - Câmara dos Deputados
I'm wanting to use Aerogear's OAuth2 to authorize several different
services in my iOS app, but am a little confused by the "predefined config"
examples and how to use a custom config. Do I just initialize a new Config
object and pass it?
jpcguy89 aka Joe
We are facing issue when deploying agpush behind apache httpd which has the
SSL below is the config. We went through your blogs and found a similar
thread but it was in complete on how to solve the issue. We cannot expose
the aerogear server to external traffic as per the compliance.
<---Apache httpd ---->
ProxyPass "/ag-push" "http://localhost:8080/ag-push"
ProxyPassReverse "/ag-push" "http://localhost:8080/ag-push"
ProxyPass "/auth" "http://localhost:8080/auth"
ProxyPassReverse "/auth" "http://localhost:8080/auth"
<---Apache httpd ---->
mysql community 5.5
WARN [org.keycloak.events] (default task-20) type=LOGIN_ERROR,
userId=null, ipAddress=127.0.0.1, error=invalid_redirect_uri,
Notice of Confidentiality.
This e-mail is intended only for the person to whom it is addressed. If an
addressing or transmission error has misdirected this e-mail, please notify
the author by replying to this e-mail. If you are not the intended
recipient you must not use, disclose, print or reply on this e-mail.
The information contained in this email including any attachments is solely
for the attention of the addressee(s) and may be confidential. Any review,
distribution or copying of this email or any attachment is prohibited. Any
views or opinions are solely those of the author and do not necessarily
represent those of KPISOFT International / KPISOFT Technologies unless
There are two new pull requests to the AeroGearOAuth2 and AeroGearHttp
libraries to bring them up to date with the latest Xcode 8 beta (beta 3)
and Swift 2.3. They are PR #53 on OAuth2 and #70 on Http. Note that for the
Http project, PR #70 overrides previously submitted PR #67.
Once these are merged in, I plan to open new branches for iOS 10 targets
and Swift 3. Both will potentially be pretty hairy, as iOS 10 changed a
number of behaviors related to NSURL and Swift 3 contains a whole host of
changes to the language. I don't think there will be any harm in having
minimum targets for either project be at least iOS 9, but they should also
be compatible with iOS 10.