Node.js / Passport.js thoughts (was: Re: OAuth2, OpenID connect and AeroGear)
by Matthias Wessendorf
Hello team!
On Thu, Oct 9, 2014 at 4:49 AM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
> Note: Not only for Keycloak, but also compatible with other technologies
> like passport on Node.js.
Great point on being compatible with passport.js! To ensure our OAuth2
client SDKs do work against node.js (w/ passport.js), how about we build a
Node.js based version of our "Shoot-n-Share backend" ([1]), that is
protected by Passport.js?
It could be a (simple) a 'clone' of our java version. I think for Luke, our
Node.js pro, it would be a fairly simple task :)
On the client side, the Android/iOS versions of Shoot-n-Share would simply
offer a new upload target for Passport.js, instead of 'just' FB,
Google-Drive and Keycloak.
That way we will also learn how much Passport.js is actually different,
similar to what we learned on how Google/FB are different ;-)
Another interesting aspect of this is that, once we are ready to release
our OAuth2 SDKs, it would be awesome to actually ship a node.js based demo
as well, instead of just a Java-based backend demo. That would clearly
show, our client libs are working across different backend technologies.
Any thoughts?
-Matthias
[1] https://github.com/aerogear/aerogear-backend-cookbook/tree/master/Shoot
> In the end, OAuth2 is just a protocol and
> should support other servers.
>
> - Should we provide examples for OpenID connect? Or abstractions?
>
> To track this issue, we have the following Jira[3] and another for
> OpenID connect[4]. Fell free to link to your respective project.
>
>
> [1] -
>
> http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerog...
>
> [2] - https://gist.github.com/abstractj/04136c6df85cea5f35d1
>
> [3] - https://issues.jboss.org/browse/AGSEC-180
>
> [4] - https://issues.jboss.org/browse/AGSEC-190
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)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
10 years, 2 months
setting up aerogear behind nginx proxy
by chale
Hi,
I need some help. I am trying to setup aerogear behind a nginx proxy
server that has ssl enabled and I am running into issues. Anytime i try to
go to /ag-push I see this in the logs
RROR [org.apache.catalina.connector.CoyoteAdapter]
(http--10.128.93.235-8080-5) An exception or error occurred in the container
during the request processing: java.lang.RuntimeException: Unable to resolve
realm public key remotely, status = 403
at
org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(AdapterDeploymentContext.java:69)
[keycloak-adapter-core-1.0-final.jar:]
at
org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(AdapterDeploymentContext.java:55)
[keycloak-adapter-core-1.0-final.jar:]
at
org.keycloak.adapters.as7.AuthenticatedActionsValve.invoke(AuthenticatedActionsValve.java:45)
[keycloak-as7-adapter-1.0-final.jar:]
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:397)
[jbossweb-7.0.13.Final.jar:]
at
org.keycloak.adapters.as7.KeycloakAuthenticatorValve.invoke(KeycloakAuthenticatorValve.java:135)
[keycloak-as7-adapter-1.0-final.jar:]
at
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153)
[jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
[jbossweb-7.0.13.Final.jar:]
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[jbossweb-7.0.13.Final.jar:]
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[jbossweb-7.0.13.Final.jar:]
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368)
[jbossweb-7.0.13.Final.jar:]
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
[jbossweb-7.0.13.Final.jar:]
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671)
[jbossweb-7.0.13.Final.jar:]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
[jbossweb-7.0.13.Final.jar:]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
Does anyone have any advice or experience on how to go about setting up
aerogear behind an nginx proxy?
--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/setting-up-aerogear-behind-ngin...
Sent from the aerogear-dev mailing list archive at Nabble.com.
10 years, 2 months
[site] community page overhaul ?
by Matthias Wessendorf
Hi,
I realized that atm we don't link to our users list, a quick/urgent fix for
that is here:
https://github.com/aerogear/aerogear.org/pull/410
That perhaps not enough! On the 'community' link we basically include the
archive of the dev list.
What should we do with that community section? How about the following
Instead of including the archive (as part of the website), we can tweak the
'community' page a bit.
E.g. we list the different options we have for users to reach out:
** links to users/dev ML subscribe page
** links to users/dev ML archives
** info on IRC
** link to our github landing page
** info on our twitter account
I think the benefit of including this on a dedicated page, makes the info
also a bit more visible, instead of just having links to ML at the footer
of our website
What are your thoughts?
Greetings,
Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
10 years, 2 months
