You can conditionally hide endpoints using the DocInclusionPredicate. At the moment, it always returns true in the code you shared.
Here's some inspiration:
private static void ConfigureSwaggerServices(ServiceConfigurationContext context, IConfiguration configuration)
{
context.Services.AddAbpSwaggerGenWithOAuth(
configuration["AuthServer:Authority"],
new Dictionary<string, string>
{
{"Something", "Something API"}
},
options =>
{
options.SwaggerDoc("v1", new OpenApiInfo { Title = "Something API - V1", Version = "v1" });
options.DocInclusionPredicate((docName, description) =>
{
return description.ActionDescriptor.IsControllerAction() && docName switch
{
"v1" => description.GroupName == null || description.GroupName == "v1",
"v2" => description.GroupName == null || description.GroupName == "v2",
_ => false,
};
//if (!description.TryGetMethodInfo(out MethodInfo methodInfo))
// return false;
//var versions = methodInfo.DeclaringType
// .GetCustomAttributes(true)
// .OfType<ApiVersionAttribute>()
// .SelectMany(attr => attr.Versions);
//return true;
//return versions.Any(v => $"v{v}" == docName);
});
options.IgnoreObsoleteActions();
options.IgnoreObsoleteProperties();
options.CustomSchemaIds(SwaggerCustomizations.GenerateSchemaId);
options.CustomOperationIds(SwaggerCustomizations.GenerateOperationId);
});
}
Why do you even want to do that? That connection string is not visible to the public. See here
Normally you configure your db server to only allow connections from specific ip addresses and/or you take additional security measurements.
If using SQL server for example, you can take a look here https://learn.microsoft.com/en-us/sql/connect/ado-net/sql/sql-server-security?view=sql-server-ver16
if you still want to encrypt the connection string, you can try implementing your own ConnectionStringResolver to do something with String Encryption
just a shot in the dark, but did you forward the port?
https://support.abp.io/QA/Questions/5902/MAUI-BLAZOR-AbpInitializationException#answer-3a0e074c-a801-92f7-86a5-dcf830d8f500
what exactly is the error?
Hey,
it's all explained in the documentation to which the "as explained in this document" link points: https://docs.abp.io/en/abp/latest/Distributed-Locking
Distributed locking is a technique to manage many applications that try to access the same resource. The main purpose is to allow only one of many applications to access the same resource at the same time. Otherwise, accessing the same object from various applications may corrupt the value of the resources.
Can you explain what's unclear?
Can you describe a bit more? It is clearly a configuration issue, so providing as much information as possible helps us to help you :)
You wrote that this happens after deploy, so I assume we are talking about some staging/ prod environment where are the certs coming from? How did you set things up?
Hey,
I would guess that this is because of the different localization resource.
does this help? https://support.abp.io/QA/Questions/857/Overriding-localization-text-of-Abp-modules
Hey,
no, that is not possible without HEAVY customization of nearly everything abp related.
May I ask why you want to do that?
Hey,
does this help you?
https://support.abp.io/QA/Questions/5025/How-to-change-the-favicon-and-title-in-the-profile-settings-page
Please also note that you may have to clear your browser storage as the favicon may be cached (best to test a change in incognito mode)
hey,
there are different things that need to be done depending on what exactly you want to customize. From your question I am guessing that you just want to replace css.
Here's the documentation on how to do that: LeptonX Blazor WASM Customization
Volosoft Youtube Video about LeptonX Customization
Does that solve your issue?