I'd like create Azue Api App backend for web and mobile clients.
In Visual Studio 2015, I created a Azure Api App Project, but I can't choose authentication (it's disable and default is No Authentication).
How can i add Individual User Account Auth and connect a DB with my api backend?
Thanks
Should you not just create a regular ASP.net project with Web API and the Local Account authentication provided by .Net Identity?
Related
I have an asp .net core 3.1 web application that uses the MS Identity (for users) and Entity (codefirst) framework to authenticate users stored in database.
All user rights/groups etc. are stored locally and used to allow/deny access to different areas of the application.
So what I think I need is a way to allow users in my web-app to choose to authenticate using AzureAD account, and when the authentication is done, the wep-app will sign-in the local-user somehow linked to the Azure user
Is this how to do this, or can you guide me to how to do this the correct way
To achieve the above requirements, You can use Azure AD authentication & external login in your asp.net application by implementing the code in your appsettings and controller as mentioned here .
As you wanted to implement the application ,
Consider other options before storing users of your Web applications in a local database. Instead of managing users in a local database, it's best practice to store and manage user information outside of the application, such as with Azure Active Directory or Azure Active Directory B2C. Consider Identity Server if the authentication service must run on-premises. Identity Server is a member of the.NET Foundation and is OpenID certified.
To implement from scratch you can refer this blog.
Please refer the below links for the similar discussion & Documentation to get started with :-
MICROSOFT DOCUMENTATION|Secure a hosted ASP.NET Core Blazor WebAssembly app with Identity Server
SO THREAD|Implement both Individual User Accounts and Azure AD Authentication & .NET Core Identity Server 4 Authentication VS Identity Authentication
BLOG| Integrating with External identity Providers
I'm going to build a .NET Core Web API (with a SQL Server database) as the backend application and react SPA as the frontend application.
For authentication, Firebase will be used.
In this project structure, where should I store additional user profile information? In Firebase or in my SQL Server database?
And should I use the builtin Identity tables to have a mapping between Firebase and my backend application (using IdentityDbContext or ApiAuthorizationDbContext) or create my own tables?
I'm developing a blazor web application that will use windows authentication. The web application requires data from another web service. Basic authentication is required on the web service. The web application and web service are in the same domain using the same domain for authentication. Is there a way to take the windows auth credential that the web application will possess and convert it to the basic auth required by the web service?
I am aware that the windows auth credential does not contain the password and basic auth needs a password. I cannot change the authentication scheme of the web service. I cannot spin up a new instance of the web service with a different authentication mechanism. I can't use basic authentication for the web application. The web service requires that the web application connects with it using the logged in users credentials for logging purposes ie. can't just use a service account to connect to the web service. I am open to using a different authentication mechanism for the web application with comparable security to windows auth if it will work, SSO preferred.
I believe this is technically infeasible but would welcome any evidence to the contrary.
We're trying to develop an ASP.NET Core web API which lets users authenticate through Azure AD and would like to retrieve files from NextCloud on behalf of this Azure AD user. Our infrastructure is composed of an Ubuntu server running NextCloud 12, a Windows Server running the ASP.NET Core web API and an Azure Active Directory instance with Azure AD Domain Services.
Signing in through NextCloud using LDAP (provided by AAD Domain Services) works without any issues.
We've been trying out SSO with SAML in addition to LDAP but we keep seeing this error message when signing into NextCloud:
Account not provisioned.
Your account is not provisioned, access to this service is thus not possible.
How exactly are we able to retrieve files from NextCloud by using the same Azure AD token we receive when authenticating with our ASP.NET web API?
SAML is not well versed to use with Web APIs - its protocol is heavily vested on the application being Web Apps - ideally you should use Open Id Connect with Jwt tokens.
I am new in dealing with Sharepoint Server and other office services. Sorry if my question doesn't make sense. My question is:
Can I use other authorization servers other than azure ACS as an access token issuer for Sharepoint 2013 apps ?
I would like to apply OAuth authentication mechanism to the SharePoint sites which are currently accessible by enabling basic authentication of site properties.
SharePoint 2013 supports for server-to-server authentication and app authentication by utilizing and extending the Open Authorization 2.0 (OAuth 2.0)
I am trying to have app authentication to access sharepoint resources(site users) with OAuth mechanism. Is it necessary to register my app on Azure ACS just to get OAuth tokens. Can I also use other auth server which can generate OAuth access token. If yes, how will they app, custom auth server and sharepoint communicate each other?