Starts in:
2 DAYS
3 HRS
39 MIN
0 SEC
Starts in:
2 D
3 H
39 M
0 S

Activities of "MichelZ"

  • ABP Framework version: v6.0.2
  • UI type: Angular
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes

I haven't found the answer to this... with Identity Server it was possible to use Azure AD to log into ABP. Is this still possible while using OpenIDDict?

We are in the process of migrating from IDS to OpenIDDict, but we haven't found a documented answer for this yet...

Thanks

I think for CORS you need to use * instead of {0}

One more question, is there an easy way to extend the Tenant class? I want to add some properties and data columns to it.

Have you looked at this? https://docs.abp.io/en/abp/latest/Module-Entity-Extensions

Yes, according to the GitHub issue this should be enough. (Also make sure you have Redis configured correctly)

No need to change anything in the background service level code.

https://github.com/abpframework/abp/issues/10322

Nevermind.... this was actually a deployment issue. The latest version didn't deploy properly, that's why I wasn't able to see the menu items :)

Looks like this is working now!

  • ABP Framework version: v5.1.1
  • UI type: Angular
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): yes
  • Exception message and stack trace:
  • Steps to reproduce the issue:"

We have upgraded to 5.1.1 and one of the features we're interested in is Impersonation. This worked well in aspnetzero for us. We have added the "Impersonation" Claim Type to the _App application.

However, we can't see any sign of Impersonation in the Angular UI. There are no permissions to set, there are no impersonation options.

We have looked at the documentation here: https://docs.abp.io/en/commercial/latest/modules/account/impersonation#angular

The documentation is fairly thin, some more description on HOW to impersonate users would also be great.

We found some of the 5.1.2 packages has some directory separator problem and we'll fix it very soon.

Interesting. We do see issues as well currently involving some of these packages, but our MO is a bit different. We get

@MichelZ, I am guessing you are using mac. Seems like the same problem with different error message.

We are using docker, so it's linux. But yes, seems like the same problem.

Interesting. We do see issues as well currently involving some of these packages, but our MO is a bit different. We get

#131 15.06 /usr/share/dotnet/sdk/6.0.101/Microsoft.Common.CurrentVersion.targets(2304,5): warning MSB3106: Assembly strong name "/root/.nuget/packages/volo.abp.commercial.core/5.1.2/lib/netstandard2.0/Volo.Abp.Commercial.Core.dll" is either a path which could not be found or it is a full assembly name which is badly formed. If it is a full assembly name it may contain characters that need to be escaped with backslash(\). Those characters are Equals(=), Comma(,), Quote("), Apostrophe('), Backslash(\). [/src/src/company.product.Domain.Shared/company.product.Domain.Shared.csproj]

however it might as well be because the packages can't be downloaded properly...

We are experiencing the docker issue, too.

Showing 21 to 30 of 55 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06