For the server side:
Unfortunately, C# servers don't expose authentication API yet (only C++
does). In order to authenticate the calls on the server side, you need to
inspect contents of request headers (and look for the right metadata
elements that contains the auth token) in your handlers and then call the
code that validates the tokens (probably part of IdentityServer).
Once the server side authentication API is in place, you should be able to
register a callback that validates the auth tokens for all incoming calls,
so that you don't need to invoke the validation code in each handler
Here's the issue to track:
On Mon, Sep 12, 2016 at 6:59 PM, Andrius Norkaitis <and...@gmail.com> wrote:
> Is there any guidance on how to add support to our own OAuth
> authentication? We plan to use https://github.com/
> IdentityServer/IdentityServer4 with Hybrid Flow and we are evaluating if
> is feasible to make the native clients (Android/iPhone) communication with
> our servers (.Net C#) by using grps but we are concerned about the
> Best regards,
> 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 grpc-io+unsubscr...@googlegroups.com.
> To post to this group, send email to email@example.com.
> Visit this group at https://groups.google.com/group/grpc-io.
> To view this discussion on the web visit https://groups.google.com/d/
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.