I am new to the IdentityServer V3. I am not sure where to find the admin page where we provide the clientID ,clientSecret and the scope etc similar to v2. Is that changed in v3? If so can someone point me to some basics?
Thanks
Check out this tutorial identityServer v3 membershipreboot-angularjs-webapi-2-and-mvc-mix. You will be most interested in Part 1. There is also sample code for this tutorial (you will find link on page).
Thinktecture has greate samples repository. Try IdentityServer3.Samples MembershipReboot example, it may be usefull for you.
Their are two https://github.com/IdentityServer/IdentityServer3.Admin and https://github.com/IdentityServer/IdentityServer3.Admin.EntityFramework repositories , both implemented backend API.
From https://github.com/IdentityServer/IdentityServer3/issues/110 brockallen commented on Oct 28, 2014
I think this issue requires me to split the EF repo into two: 1) for
the EF entities, and 2) implementation of the Core interfaces that
maps back and forth from core to EF entities. Then I'd add a third
project/repo that references the EF entities and build interfaces that
map back/forth to the Core.Admin interfaces/models
You either need to implement UI by yourself, or buy a AdminUi product https://www.identityserver.com/products/
Related
I have several services, each one exposed through REST API with ASP.NET Core Web API. I use Swashbuckle for ASP.NET Core tooling in order to automatically generate from my controllers and DTOs all the necessary documentation and visualize it in SwaggerUI. I found this tooling really great, with little annotations on my models and my controllers already provides many features out of the box, such as a UI client to try out the REST API endpoints.
But with this solution each service has its own dedicated SwaggerUI instance and therefore UI.
I would like to offer to my customers a wiki-like documentation with a navigation menu, where, for instance, they can browse sections regarding all the endpoints exposed by my services and have on each page the same features offered by SwaggerUI.
It can be achieved by creating my own web application but I was wondering whether an out of the box solution or some tool that might ease such integration already exists.
I tried Slate but I felt like I had to re-invent the wheel in order to automate at least the creation of the basic API documentation, namely controller definition, response definition and descriptions. Does anyone have any suggestion?
I faced this very issue recently working in a microservices architecture, you're absolutely right. There is not need to reinvent the wheel.
I really can't recommend redoc by Redocly enough in this case.
Have a look at the multiple-apis example.
We have a WCF Odata Service enabled. We are planning to migrate to Web API2. I was told we are not going to user Odata.
Could someone enlighten me on, why shouldn't we use Odata. Is it going to obsolete soon. What are the downsides of using it, and can we use it without Entity Framework. Please suggest a good tutorial. Thanks.
This article https://learn.microsoft.com/en-us/aspnet/web-api/overview/odata-support-in-aspnet-web-api/odata-v4/create-an-odata-v4-endpoint was written less than a month ago, so I can't see any reason why you couldn't use Odata in Web API2. Shouldn't is just an opinion and not really what this site is for. I'd recommend asking whoever made the decision for their reasons.
As for a good tutorial, the article I just linked seems like a fairly good place to start.
From the article:
Web API OData does not require EF. Use any data-access layer that can translate database entities into models.
I am having a bit of an issue with integrating with NetSuite API on .Net Core using VS2017 and it has no option to add Web Service. When I consumed their web service using add connected services some objects and classes are missing.
In .Net 4.5, the classes and object are available. My manager wants me to write the API in .Net Core.
I took the sample code from NetSuite and the very first thing is class NetSuiteService which has important Passport property for login.
Anyone had a solution to this?
It's fairly easy to integrate SuiteTalk with Dot NetCore, all you need to do is import the WSDL into .NetCore project via adding it as ConnectedService reference and it will set you up with WCF.
The DEMO code that NetSuite people have provided will not match the code generated on your machine. I would recommend you using TBA instead of other authentications.
(just copy paste the code provided by NetSuite's folks for authentication as that is the convention, you can change the crypt algorithm if you want to, just generate the Keys, put them in your configs and you're good to go)
Class "NetSuitePortTypeClient" will contain your endpoints for all types of communication to NetSuite web services.
Read the first 50-100 pages of the documentation manual that NetSuite provides for learning the conventions to be used throughout your journey.
Hope this will give you a headstart.
Our company has an SSO app that I'm looking to replace a significant chunk of the authentication pipeline with IdentityServer4 or 3. The version I'm replacing has its own custom implementation of Dynamic Client Registration (not to spec) and a UI to manage it.
There are a number of Github issues across the IdentityServer project discussing the issue and the resolution appears to be that it hasn't been implemented and someone looking to use DCR should write their own implementation of the spec as an extension.
Am I correct that this is currently not possible and I would be better served creating my own DCR extension on Github for IdentityServer? Or have I missed something with my Google-fu and someone's already written an extension?
Note I'm happy to implement my own if it's necessary.
IdentityServer 4 does not provide any implementation of dynamic client registration as they consider it out of scope for the project.
However you can implement your own, either as a middleware or as a MVC controller.
You need an endpoint that uses ConfigurationDbContext to the Clients table.
Source code for this is a issue on GitHub.
https://github.com/IdentityServer/IdentityServer4/issues/1248
IdentityServer itself (the STS) has no implementation of OIDC DCR
https://openid.net/specs/openid-connect-registration-1_0.html
This is more of an admin type functionality.
The Azure AD team has a sample which authenticates against the AAD common endpoint and uses the returned claims to automatically provision new tenants. It might be a good place to start...
I have created a webapi 2 service that I need to secure. I am trying to use the Individual Accounts in VS2013 but I after much research I cannot figure out how to:
a. Customize the User model with my own properties (no such class exists in template)
b. Get access to User and Role contexts
I tried using the nuget's EFMembershipCodeFirst package but I noticed its deprecated, this package provided access to the required classes (User/Role).
There are plenty of examples for Mvc but I'm using Angularjs as the front end.
Does anyone know how I can customize the User model that vs2013 Individual Accounts template creates? Maybe I'm missing something obvious? I'm a bit of newbie when it comes to securing webAPIs. Thanks
Edit: UserManage.Create() only takes a password and a username, I need override it to also accept myUniqueId. Any thoughts?
Updated title for clarity + added image.
The classes you should concentrate on are the IdentityUser, UserManager and RoleManager classes.
This example shows you how you can use them.
Because your using AngularJS an option would be to create an ASP.NET Web API backend.
The official documentation is a good starting point to become familiar with ASP.NET Identity.
As per #Horizon_Net's suggestion, I created a custom class that derived from IdentityUser, but used the following as guidance:
Here