AspNet.Security.OpenId.Providers | OpenID 2.0 authentication middleware for ASP.NET Core | Authentication library

by aspnet-contrib PowerShell Version: 7.0.0 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | AspNet.Security.OpenId.Providers Summary

AspNet.Security.OpenId.Providers is a PowerShell library typically used in Security, Authentication applications. AspNet.Security.OpenId.Providers has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

AspNet.Security.OpenId.Providers is a collection of security middleware that you can use in your ASP.NET Core application to support OpenID 2.0 authentication providers like Steam or Wargaming. It is directly inspired by Jerrie Pelser's initiative, Owin.Security.Providers.

Support

Quality

Security

License

Reuse

Support

AspNet.Security.OpenId.Providers has a low active ecosystem.

It has 190 star(s) with 38 fork(s). There are 13 watchers for this library.

It had no major release in the last 12 months.

There are 3 open issues and 53 have been closed. On average issues are closed in 438 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of AspNet.Security.OpenId.Providers is 7.0.0

Quality

AspNet.Security.OpenId.Providers has 0 bugs and 0 code smells.

Security

AspNet.Security.OpenId.Providers has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

AspNet.Security.OpenId.Providers code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

AspNet.Security.OpenId.Providers is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

AspNet.Security.OpenId.Providers releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 77 lines of code, 0 functions and 32 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of AspNet.Security.OpenId.Providers

Get all kandi verified functions for this library.

AspNet.Security.OpenId.Providers Key Features

No Key Features are available at this moment for AspNet.Security.OpenId.Providers.

AspNet.Security.OpenId.Providers Examples and Code Snippets

No Code Snippets are available at this moment for AspNet.Security.OpenId.Providers.

Community Discussions

Trending Discussions on AspNet.Security.OpenId.Providers

ASP.Net Core 2.1 IdentityCore (Role Claims not being added on user sign in)

ASP.Net Core OpenIdConnect Steam

QUESTION

ASP.Net Core 2.1 IdentityCore (Role Claims not being added on user sign in)

Asked 2018-Oct-17 at 15:04

I'm using ASP.Net Core 2.1 with IdentityCore Service, the application is a pure API, no views at all. For authentication I'm purely using Steam authentication (No User/Pass login) provided by, https://github.com/aspnet-contrib/AspNet.Security.OpenId.Providers

This API has been created to fit a very specific authentication workflow (User's can only login to the API with Steam) the Angular SPA sitting as the frontend handles the workflow just fine.

The problem is that when I add a Role to a user (I've already got roles seeded and I've added my own steam account to the Admin Role), the role type claims are not being added on login, therefore when an admin user attempts to access an API route protected by [Authorize(Roles = "Admin") I'm being returned an Unauthorized Redirect.

Below I have added all code snippets I think is required (feel free to request more).

If I use (I am currently using this as a temporary solution, but it is not ideal for future development);

...

ANSWER

Answered 2018-Oct-17 at 15:04

You have tow way for this issue.

When you send a request to any WebService, If you set, Authorization be run Now:

Before login If you want to send a request to your WebService, and want to ignore Authorization you have to use of Allowanonymus Attribute like:

[Allowanonymous] Public void Login() { // here }

With this attribute, Authorization will ignore the request.

Now! If you want to send a request after login, you should to create you cookie In login time, and send a response to client, and also you have save that cookie in your localStorage in client, for Identifying in client. After this you have to set that cookie in header of every request. With this way, you authorization will Don!

Now If you want, I can create a sample for Authorization in best practice.

Source https://stackoverflow.com/questions/52686139

QUESTION

ASP.Net Core OpenIdConnect Steam

Asked 2017-Jun-11 at 19:24

I'm trying to implement Steam OpenId into my ASP.Net Core application, and I don't have any previous experience implementing OpenID.
Unfortunately, Steam is massively lacking documentation on their side, and simply state "just download an OpenID library", and provide you with a page to register an API key for a domain name.

There are several implementations available for full ASP.Net, but not for Core, and it seems there are some differences.

I'm trying to use Microsoft.AspNetCore.Authentication.OpenIdConnect, though I am not entirely sure if this is the right library. It seems there is a difference between "OpenID" and "OpenID Connect".

I've set up the authentication in my Startup.cs like so:

...

ANSWER

Answered 2017-Jun-11 at 19:24

It seems there is a difference between "OpenID" and "OpenID Connect".

There is: OpenID 1/2 and OpenID Connect are totally different protocols.

Steam is still using OpenID 2.0 so you can't use ASP.NET Core's OpenID Connect middleware to authenticate your users using their Steam account, as the two protocols are not compatible/interoperable.

I know this question isn't very specific, but can anyone point me in the right direction with this? I am a little stumped.

The aspnet-contrib Steam middleware you've mentioned derives from a generic OpenID 2.0 provider specially developed for ASP.NET Core and thus is probably your best option (that said, I'm the guy who's written it, so I'm likely not objective).

You can find the package on NuGet.org: https://www.nuget.org/packages/AspNet.Security.OpenId.Steam/.

Source https://stackoverflow.com/questions/44487710

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install AspNet.Security.OpenId.Providers

Adding external authentication to your application is a breeze and just requires a few lines in your Startup class:. See the /samples directory for a complete sample using ASP.NET Core MVC and supporting multiple external providers.