OpenID Connect Integration with template - aspnetboilerplate

I've got a question on the best way to implement OpenID with aspnetboilerplate.
I've looked and browsed on the net and I can't seem to find anything that is clear cut to me.
I'm wondering if Has anyone got some OpenID example code to implement with Aspnet boiler plate?
I already have a Identity Service instance I need to log in to, but I can't see the way I'd hook up my project too it.
I've tried looking at the external providers documentation documentation, but that doesn't seem to list it in the JWT External Auth providers.

Related

How can we use Apple Provider with Spring Security oauth2 client

I need to use Apple_Sign_In option with other Google, Facebook sign in options. Even though Apple is adopted the existing open standards OAuth 2.0 and OpenID Connect (Hybrid Flow). It's difficult to get it work by simply changing the .yml configurations as described in GitHub fix for raised issue..
I have tried Customizing oauth request approach and I am stuck on reading Authorization code which is sent in body to use for token exchange and get logged user details(Apple does not support userInfoUri.)
More details can be found on github_comment
Can someone share a working code example how can we use Apple Sign In with oauth2 client ?

Spring RESTful web service auth

I am learning Spring and have written a simple RESTful web service that is not intended for browsers but for native mobile apps only. When trying to implement basic authentication for users. I've hit a wall, because the sources (even official tutorials) assume (and recommend) using OAuth2 through a browser with SSO and\or social logins.
All I want is to create an API RESTful endpoint that will take an email address and a password and return a token (possibly JWT). I do not need extended support for roles (but am not against it) and dynamic token revokation if that matters.
Is there any easy library/solution/tutorial that focuses on something similar?
Edit:
Thanks for the answers — all of them shed more light on the auth process and are quite useful and on point!
Please check here, I have a working example for the spring security on my github. You may need to change the spring.active.profiles=jwt, to enable the jwt configurations on this project.
There are many tutorials available on internet for implementing JWT token based authentication using Spring Boot. Please find below some of them
https://dzone.com/articles/spring-boot-security-json-web-tokenjwt-hello-world
https://www.javainuse.com/spring/boot-jwt
Please go through them and try to implement. If you need a working code for reference, you can search GitHub for code. This is one of them https://github.com/murraco/spring-boot-jwt

Linking Auth0 and Parse Server users

I am writing an app that uses Parse Server, with Auth0 as the authentication provider. For unrelated reasons, we need to use Auth0 rather than Parse for user management.
I'm having trouble figuring out how to "link" a user authenticated via Auth0 to Objects in Parse Server. Without this, the authenticated user will not have permission to write to his/her Objects on the Parse Server. I believe my issue is similar to this question, which has no solution: here.
I have found many articles discussing the migration of users from Parse to Auth0, but am finding surprisingly little documentation on how to link those users to Parse. There is one article (I believe written by the same person who posted the question I linked to), but I couldn't get it to work, and it involves storing passwords in cleartext in Javascript.
I thought to create a default Parse user that would simply own all the objects in Parse. This would be invisible to the authenticated end-user so they wouldn't know, but that's just security by obscurity and doesn't seem like a good approach.
If anyone has suggestions on how to approach this, or has done it before, I'm interested to read your suggestions. Thank you very much.
Auth0 supports the most common and used authentication protocols (OAuth2/OIDC, SAML and WS-Federation) so configuring an application to rely on Auth0 is really easy when that application already talks one of the previously mentioned protocols.
According to the Parse Server Wiki, it does support custom authentication leveraging OAuth so that seems your best starting point for integrating Auth0 with a Parse Server based application.
It is possible to leverage the OAuth support with any 3rd party authentication that you bring in.
Disclaimer: I never used the Parse service or Parse Server so I'm assuming that when you mean linking Parse objects to users this can be accomplished by simply having an authenticated user in Parse and the identity of that user is just verified and proven by Auth0 instead of something like built-in username/passwords managed by Parse itself.

Moving from Web API 2 Claim-Based-Authentication to ThinkTecture

I am finding that Microsoft's implementation of Claim-Based Authentication is not really up to the expectation of the true Claim-Based setup, and I seems like ThinkTecture is doing a good job of replacing Web API implementation.
I am wondering if anyone has a guide or blog post for people to move from the default SPA Template for VS2013 for AccountController to the ThinkTecture approach.
I also like that default Microsoft Web API AccountController that will create the tables for AspNetUsers and Roles, but I am not sure if ThinkTecture does the same thing or not.
I guess I am a little confused between all of the repositories that ThinkTecture have. Does any one have a solid guidance in terms of what to use, IdentityServer, IdentityModel.45, or AuthorizationServer?
I am just looking to drop the whole Microsoft approach and open to use a proper true Claim-Based approach, but I kinda need help in terms of EF6 migrations for the Identity tables, and what projects to use, or how to drop the the whole AccountController approach in SPA-Template for VS2013. I have looked at Dominick's blog and it seems to be really good, but I haven't found a post that kinda helps moving from Web API approach to ThinkTecture way of thinking.
Thinktecture Identity Server is for issuing authentication tokens (for things like websites) and is helpful for SSO (again, in browser scenarios).
Thinktecture Authorization Server is for issuing authorization tokens (for things like Web APIs). Authorization Server needs the user to authenticate, and so it can rely upon Identity Server for that.
Thinktecture IdentityModel is a helper library you'd use in either a web app or Web API app to help with various security concerns that aren't provided by the .NET framework.

OpenId and OpenAuth with mvc application

I need to login with facebookx, twitter, gmail, openid, yahoo and other site in MVC3.
I already search for Openauth and openID but could not get the proper solution. come solution run and went to the site but never come back with identty.
So can i get the proper solution in running mode with MVC3. Also please provide me the dll and also nuget template or packages details.
Can i test with localhost for openauth/openid?
In short, Yes you can test and host on local host.
What you need to focus is a Tokens that are managed in OAuth library provider of your choice. Just follow the wiki and some tutorial and you will be fine.
As a start point look at the dotnetopenaut.net source library that brings OpenID, OAuth, and ICard capabilities to the Microsoft .NET Framework.
Reference: look at this post for more details: OpenID and OAuth using DotNetOpenAuth in ASP.NET MVC

Resources