"For the oauth integration on the client, you would need an adapter similar to the one that we have for grpc.credentials.createFromGoogleCredential for our auth library." Is the any exampled available how to impalement it? I'm looking forward to see how to add OpenID Connect to grpc c# server with IdentityServer4.
2016 m. liepa 13 d., trečiadienis 03:15:57 UTC+3, Julien Boeuf rašė: > > +Michael (node) > +Jan (C#) > > Hi Gutemberg, > > We have a nodejs implementation of gRPC already so I guess, it would make > much more sense to use this one on the client since threading is typically > difficult to get right between node and C++ (2). For the oauth integration > on the client, you would need an adapter similar to the one that we have > for grpc.credentials.createFromGoogleCredential for our auth library. > > On the server side, you would extract the metadata, get the authorization > header/metadata and pass that to your external library for verification > before granting access. > > Cheers, > > Julien. > > On Tue, Jul 12, 2016 at 4:28 PM, Gutemberg Ribeiro <[email protected] > <javascript:>> wrote: > >> Hello Julien and thanks for get back. >> >> >> >> Our client is basically a node.js/chromium application(electron.atom.io) >> embbeded on the ARM device. >> >> >> >> Out server is a C# webAPI which is basically RPC and we want to move it >> to use a solid RPC framework, and that is why we are reaching you guys out. >> >> >> >> In order to achieve that, we need to replace our server from a webAPI to >> a C#-based gRPC service and, implement the client, and implement the Oauth >> support on both ends, by integrating it with IdentityServer for client >> credentials so the client just make follow the client_credentials flow, and >> push the token to the server which in turn, should grab that token and push >> the IdentityServer in order to validate that token and obtains the client >> claims for authorization. >> >> >> >> Our client application is basically Javascript code and since it is based >> on node.js we can (1) use any pre-existent client for node.js/JS or (2) use >> gRPC C++ as a node.js native plugin so we can call its native lib from the >> JS world. >> >> >> >> Is that possible? >> >> >> >> Thanks >> >> Gutemberg >> >> >> >> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for >> Windows 10 >> >> >> >> *From: *Julien Boeuf <javascript:> >> *Sent: *Tuesday, July 12, 2016 8:14 PM >> *To: *grpc.io <javascript:> >> *Cc: *[email protected] <javascript:> >> *Subject: *Re: Custom OAuth authentication with grpc >> >> >> Hi Gutemberg, >> >> Which language are you using on the client side? >> >> There is a way to extend client credentials documented here (for C++): >> >> http://www.grpc.io/docs/guides/auth.html#extending-grpc-to-support-other-authentication-mechanisms >> >> The other wrapped languages should be able to use a similar API. >> >> Julien. >> >> On Wednesday, June 29, 2016 at 3:00:55 PM UTC-7, Gutemberg Ribeiro wrote: >> >> Hello guys, >> >> >> >> Is there any guidance on how to add support to our own OAuth >> authentication? Our servers today use >> https://github.com/IdentityServer/IdentityServer3 with >> client_credentials flow and we are evaluating if is feasible to make our >> device >> communication with our servers (.Net C#) by using grps but we are concerned >> about the authentication. >> >> >> >> I saw in the docs that Oauth is used but only for google services and we >> would like to customize it to use our own. Is there any guidance? >> >> >> >> Thanks! >> >> Best regards, >> >> >> >> Gutemberg >> >> >> >> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for >> Windows 10 >> >> >> >> > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/a9a81e73-e1db-4ce0-bac3-f67c453b989d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
