AppText has two authorization modes:
- full access to API, Admin interface and all Apps based on the ASP.NET Core host application configuration in Startup.cs;
- read-only access to the REST and GraphQL API's based on an API key that is created with the Admin interface for a single app.
That's it. No users, no roles, no groups.
This page covers full-access authorization via the host application. See API key authorization how to configure read-only API access.
AppText itself is completely security-agnostic. It depends on the configuration of the host application. This way all ASP.NET Core authentication methods are supported out of the box. ASP.NET Identity with local accounts, AzureAD, IdentityServer, everything is possible.
There are two configuration settings for AppText that link it to the Authentication and Authorization configuration of the host application:
This is a simple configuration option that simply says: 'anonymous access to AppText is not allowed, but any authenticated user can do everything'.
Use this only when you don't have any extra requirements about who can access AppText. Most of the times you'd probably be better off with a custom authorization policy and link that to AppText with the
Authorization policies in ASP.NET Core are a very powerful and flexible way to secure applications. When setting the RequiredAuthorizationPolicy option, you're applying a single authorization policy to all of AppText.