@mightyit the documentation has been moved to https://docs.aspnetzero.com/documents/aspnet-core-angular/latest/Features-Angular-User-Menu#linked-accounts
Hi, are you using jquery version ANZ? If so what is your project version?
Can you share the http responses from both API? Did both of them contain the user friendly message?
if possible, please share the code for both API call/usage in your application.
you can use the new health check features in ANZ 7.1.
The Health Check does have support for hangfire.
e.g. maxium failed job count, minimum available server
see more options at https://github.com/Xabaril/AspNetCore.Diagnostics.HealthChecks/blob/master/src/HealthChecks.Hangfire/HangfireHealthCheck.cs
@mightyit yes. service proxies are generated via NSwag for angular project.
Hi @knappnpm, you need to login with your github account associated with your aspnetzero license to view url.
you can do it at https://aspnetzero.com/LicenseManagement
Hi @aprsystem, you need to login with your github account associated with your aspnetzero license to view url.
you can do it at https://aspnetzero.com/LicenseManagement
Hi, have you tried configuring swashbuckle as follows?
options.DocInclusionPredicate((docName, apiDesc) =>
{
if (!apiDesc.ActionDescriptor.IsControllerAction())
{
return false;
}
switch (docName)
{
case "v1":
return apiDesc.GroupName == null || apiDesc.GroupName == "v1";
case "v2":
return apiDesc.GroupName == null || apiDesc.GroupName == "v2";
default:
return false;
}
});
it was discussed on https://github.com/aspnetboilerplate/aspnetboilerplate/issues/3814#issuecomment-418118210
Hi, did you use ANZ default login?
or the login was done via a different authencation provider?
Hi @amplicade, can you also share the code for PersonAppService
that you have created as per the tutorial intructions?
if the API does not appear in swagger, it means the app service was not recognized by swagger as an endpoint, therefore when you refresh via nswag, the classes used in the app service will not be included in the service proxies.
Hi @jfirth, if you doesn't want to use LDAP as external authentication source, you can implements your custom Azure AD external authentication source (using client id and key) by inheriting DefaultExternalAuthenticationSource and overrides the TryAuthenticate
with the client id and key authentication.