Activities of "rcalv002"

I have removed the dynamic section and can see it present. Attempting to login with the microsoft acc in the production deployment generates an invalid uri error, because the auth server returns http instead of https which is not allow. We had something similar in the past with identity server and implemented a workaround for it, here https://abp.io/support/questions/3706/Identity-server-production-deployment-with-angular. However this didnt work on iddict, We attempted to fix this with the following but it doesnt work: the value for app:selfurl is the https address in the docker container, the service is still behind nginx proxy so those configs have not changed.

public override void PreConfigureServices(ServiceConfigurationContext context)
{
    var hostingEnvironment = context.Services.GetHostingEnvironment();
    var configuration = context.Services.GetConfiguration();

    ...

    PreConfigure<OpenIddictBuilder>(builder =>
    {
        builder.AddValidation(options =>
        {
            options.AddAudiences("CloudTools");
            options.UseLocalServer();
            options.UseAspNetCore();
            options.SetIssuer(configuration["App:SelfUrl"]);
        });
    });

   ...
}

Sign in Sorry, but we’re having trouble signing you in.

AADSTS50011: The redirect URI 'http://mydomain.com/signin-microsoft' specified in the request does not match the redirect URIs configured for the application 'myappid'. Make sure the redirect URI sent in the request matches one added to your application in the Azure portal. Navigate to https://aka.ms/redirectUriMismatchError to learn more about how to fix this.

If we login with regular auth, and then go to settings -> external providers we can then enable a checkbox for microsoft and type in the id and secret again at which point it works. but it seems this should be automatic because its configured in code?

• ABP Framework version: v8.1.0
• UI Type: Blazor Server
• Database System: EF Core
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace:
• Steps to reproduce the issue:

Attempted to implement social login on our app. as per docs below but the login button doesn't appear when we go to the login page. What's missing?

context.Services.AddAuthentication()
    .AddMicrosoftAccount(MicrosoftAccountDefaults.AuthenticationScheme, options =>
    {
        options.AuthorizationEndpoint = "https://login.microsoftonline.com/guid/oauth2/v2.0/authorize";
        options.TokenEndpoint = "https://login.microsoftonline.com/guid/oauth2/v2.0/token";

        options.ClaimActions.MapCustomJson("picture", _ => "https://graph.microsoft.com/v1.0/me/photo/$value");
        options.SaveTokens = true;

        options.ClientId = configuration["Authentication:Microsoft:ClientId"];
        options.ClientSecret = configuration["Authentication:Microsoft:ClientSecret"];
    })
    .WithDynamicOptions<MicrosoftAccountOptions, MicrosoftAccountHandler>(
        MicrosoftAccountDefaults.AuthenticationScheme,
        options =>
        {
            options.WithProperty(x => x.ClientId);
            options.WithProperty(x => x.ClientSecret, isSecret: true);
        }
    );

• Template: app
• Abp version: 9.0.0
• Created ABP Studio Version: 0.9.11
• Tiered: No
• UI Framework: blazor-server
• Theme: leptonx
• Theme Style: system
• Database Provider: ef
• Database Management System: sqlserver
• Separate Tenant Schema: Yes
• Mobile Framework: maui
• Public Website: Yes
• Optional Modules:
  • GDPR
  • TextTemplateManagement
  • LanguageManagement
  • AuditLogging
  • SaaS
  • OpenIddictAdmin

• Steps to reproduce the issue:

generate new app solution with abp studio Add a method to an appservice Execute method via swagger Receive antiforgery token error.

2024-11-22 11:36:09.728 -07:00 [WRN] The required antiforgery header value "RequestVerificationToken" is not present.
2024-11-22 11:36:09.729 -07:00 [INF] Authorization failed for the request at filter 'Volo.Abp.AspNetCore.Mvc.AntiForgery.AbpAutoValidateAntiforgeryTokenAuthorizationFilter'.
2024-11-22 11:36:09.730 -07:00 [INF] Executing StatusCodeResult, setting HTTP status code 400

Was this broken again with the move to 9?

similar to old post where this was already fixed in v4 https://abp.io/support/questions/554/REST-API-Antiforgery-Cookie-Error-After-POST-apiLogin---POST-apimyentity-Call-Sequence

We don't want a user to login, as our addon will run for many users and all of the communication that addon initiates with the abp backend, should be for the same tenant (but not specific to the user). Our addon will be used by many tenants in the same environment, the tenant's configuration details would be saved in the db the addon connects to (separate from abp) and retrieved on addon startup to make api calls to abp backend using the dynamic proxy application services. Could you help us with a poc for this?

hi

Both Dynamic C# API Client Proxies and Static C# API Client Proxies can be used.

https://abp.io/support/questions/1727/How-to-build-winform-application-client-for-Dynamic-C-API-Client-Proxies

@mali, I think the question focuses most on the appropriate way to use the same and ensure the client is communicating with the correct tenant.

the service is one saas, and each customer will receive the client application, they will have to plug in some configuration values like the application id/ secret etc. And how to make sure their client only communicates with their tenant data?

as you can see our module solution comes from the previous abp design of modules where there were the **src **projects and the several **host **projects in the module solution. to completely develop and test the module we use the host solution as we would an "application" solution. therefore the module and host have the dependencies we plan to use once we integrate our module into any other app solution. for example this module can be integrated to 3 4 5 other app solutions (at least that was the idea with modules right?)

I see in the latest version of solutions generated now by abp studio (since we can no longer generate anything in suite), creation of module doesnt have any host project and its just library projects for app project, but that means usability amongst other app projects is out of the question?

Either way, if you're saying from now on our module projects cannot use already implemented modules from abp, then how do we code functionality in our modules that consumes that? for example the module provides all of the functionality related to docusign, like the app services that are exposed, events that are triggered and jobs that are handled, not the application project the application solution will bring in other modules that provide their respective functionality like this..

Could you provide a process or flow of how we should develop these modules to make sure they don't clash?

Also, could you provide a process flow for how you found the root problem in this ticket? It will help us with our troubleshooting before opening tickets in the future.

I added this and i can see entry in debug log during project startup regarding hangfire. two questions

1. After adding this, project just hangs on start up and then stops. This appears in the log

Hangfire.SqlServer.SqlServerObjectsInstaller: Information: Hangfire SQL objects installed.
Hangfire.BackgroundJobServer: Information: Starting Hangfire Server using job storage: 'SQL Server: (LocalDb)\MSSQLLocalDB@Cloudapps'
Hangfire.BackgroundJobServer: Information: Using the following options for SQL Server job storage: Queue poll interval: 00:00:00.
Hangfire.BackgroundJobServer: Information: Using the following options for Hangfire Server:
    Worker count: 20
    Listening queues: 'docusignsignatures', 'default'
    Shutdown timeout: 00:00:15
    Schedule polling interval: 00:00:15

2. I've never had to add this before in any project, is this a new requirement? is it documented?

I reshared projects with you

Mailed you