Activities of "dshapiro"

For authentication we should define a new OpenID application within ABP and configure Elsa Studio to authenticate via OIDC? Or perhaps there's a simpler way to accomplish this as Elsa Server is hosted within the ABP project, so should have direct access to the Identity provider.

Thanks, I did find this but I wasn't sure if it was completely compatible with my solution as I use the Angular frontend and a *.HttpApi.Host project instead of an MVC Web project. This article also doesn't cover how to expose Elsa Studio (other than to use docker which seems unnecessary for this) and to use ABP's users and permissions within Elsa Studio.

I've followed the instructions for creating an Elsa 3 server and added this to a new Domain-level project (*.Domain.Workflows) within my ABP Solution. I've got *.Domain.Workflows referencing *.Domain (project reference and module added to DependsOn) and *.Application references *.Domain.Workflows (project reference and module added to DependsOn). While debugging I can see that the initialization logic is being executed in my new module, however the endpoint where the Elsa API should be exposed is not responding (404). It's not clear to me if ABP's configuration is somehow interfering or not.

Hoping I can get some guidance on this?

That's really strange. To the best of my awareness I didn't delete any upgrades (except for empty ones), but you're right: I don't see a way for this situation to happen otherwise.

Thanks for your help on figuring this one out!

I've resent it.

Already sent on Friday. Please confirm receipt or provide update on findings.

Hi, I sent you an email with our project attached as it would probably be easier. I believe everything we've done is standard and per ABP recommendations, but let me know.

Sorry, yes, "ExtraProperties". All projects were updated to 9.0.3 but our database does not have the column. We tried creating a migration, but it was empty. We also tried running the dbmigrator with a new database name (to generate a new database) and still did not get this new column.

To confirm, is your demo using the angular front end? I found a few things that seemed to imply that this worked for the MVC front end, but not for Angular.

I'd also like to clarify: is it possible to upgrade to ABP 9.x and use .NET Core 8? My team would like to stick to LTS versions of Core.

We've used the provided documentation in order to add a new property to the IdentityRole entity:

*Project.Domain.Shared/ProjectModuleExtensionConfigurator.cs*

public static class ProjectModuleExtensionConfigurator
{
    private static readonly OneTimeRunner OneTimeRunner = new OneTimeRunner();

    public static void Configure()
    {
        OneTimeRunner.Run(() =>
        {
            ConfigureExistingProperties();
            ConfigureExtraProperties();
        });
    }

    private static void ConfigureExistingProperties()
    {
        
    }

    private static void ConfigureExtraProperties()
    {
        /* https://docs.abp.io/en/abp/latest/Module-Entity-Extensions */

        ObjectExtensionManager.Instance.Modules().ConfigureIdentity(identity =>
        {
            identity.ConfigureRole(role =>
            {
                role.AddOrUpdateProperty<bool>(
                    RoleConsts.IsGlobalPropertyName,
                    options =>
                    {
                        options.Attributes.Add(new RequiredAttribute());
                        options.Attributes.Add(new DefaultValueAttribute(false));
                    });
            });
        });
    }
}

What we've found is that this adds a new column to the Roles table in the angular front end, but does not add the field to the create/edit Role modals. Digging some more, we found the documentation for Dynamic Form Extensions, and configured this for Roles:

*/src/app/core/prop-contributors.ts*

import { eIdentityComponents, IdentityCreateFormPropContributors, IdentityEditFormPropContributors  } from '@volo/abp.ng.identity';
import { ePropType, FormProp, FormPropList } from '@abp/ng.components/extensible';
import { IdentityRoleDto } from '@volo/abp.ng.identity/proxy';

const isGlobalProp = new FormProp<IdentityRoleDto>({
    type: ePropType.Boolean,
    name: 'isGlobal',
    displayName: 'Is Global',
    validators: () => [],
});

export function isGlobalPropContributor(propList: FormPropList<IdentityRoleDto>) {
    propList.addByIndex(isGlobalProp, 1);
}

export const roleCreateFormPropContributors: IdentityCreateFormPropContributors = {
    // enum indicates the page to add contributors to
    [eIdentityComponents.Roles]: [
        isGlobalPropContributor,
        // You can add more contributors here
    ]
};

export const roleEditFormPropContributors: IdentityEditFormPropContributors = {
    // enum indicates the page to add contributors to
    [eIdentityComponents.Roles]: [
        isGlobalPropContributor,
        // You can add more contributors here
    ]
};

*/src/app/app-routing.module.ts*

// ...
{
    path: 'identity',
    loadChildren: () => import('@volo/abp.ng.identity').then(m => m.IdentityModule.forLazy({
      createFormPropContributors: roleCreateFormPropContributors,
      editFormPropContributors: roleEditFormPropContributors
    })),
  },
// ...

Despite this, no new field is appearing on the Create/Edit Role modals.

We also considered/tried to replace the RoleComponent using component replacement, but this would require us to completely rewrite the role component and it's associated behaviour (CRUD, claims, permissions, move users, etc), which we do not want to do.

How can we achieve our goal of managing this new property within the Roles modal?

• ABP Framework version: v8.3.0
• UI Type: Angular
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes
• Exception message and full stack trace: N/A
• Steps to reproduce the issue: N/A