HttpContext.Current.User not set automatically in INavigable when using OAuth authentication

You should use Apis.Get<IUsers>().AccessingUser ( https://community.telligent.com/community/11/w/api-documentation/64105/users-in-process-api-service ) to detect the user who accessing the community in this context.

That did not seem to work for me.  I changed var User = null;  to var user = Apis.Get<IUsers>().AccessingUser and it still returned Anonymous.  Code in the original post did retrieve the correct user, so I know the OAuth bearer token was valid.

Could you provide more context within the implementation of INavigable to show where this code is executed? If AccessingUser is anonymous, the user has not been authenticated by the community.

Register the INavigable request handlers...

Determine report output type and delegate...

First, validate the request to make sure the user has the right permissions...

Validation code...

Here's the call I'm using to get the OAuth access_token to begin with...

Thank you. I see the issue now.

OAuth requests are not allowed for regular page requests. INavigable supports regular page requests only (so OAuth credentials are ignored). For page requests, AccessingUser is already populated at this point.

To enable OAuth authentication, you'll want to implement an API extension via the IRestEndpoints plugin type ( plugin type: https://community.telligent.com/community/11/w/api-documentation/65621/irestendpoints-v2-plugin-type , training article: https://community.telligent.com/community/11/w/developer-training/65113/exposing-data-to-external-sources ). Specifically, you'll want to register a REST endpoint using an override on the controller that takes a Action<IRestRequest,HttpResponse> handler--this will allow you to write raw data on the response instead of using the regular REST JSON/XML serializer.

API extensions will honor OAuth authentication headers.