Activities of "Buckoge"

Hi,

Thanks for the answer.

We'll keep using our Razor UI for users, organization units and tenants until that release.

Thanks!

For years we have been using the MVC (Razor) UI, where we added extended properties to Users, Organization Units and Tenants. In Razor they appear in the forms automatically and everything works fine.

We are now migrating our application to React, and we see that the Admin Console is a separate application. There, our extended properties are not shown at all — not in the create form, not in the edit form, not in the tables. As a result, users, organization units and tenants can no longer be created or edited: every save fails with validation errors of the form "The <PropertyName> field is required", because the form never sends those values.

Our questions:

1. Do you plan to support extended properties in the Admin Console, and roughly when?
2. If not, is there another solution you would recommend?

Thank you.

Hi,

Thank you for the explanation.

I came across this while testing and wasn’t sure of the best place to report it, so i decided to share it here. As mentioned earlier, we are still in the pre-production phase, so we’re happy to wait for the fix in the upcoming release.

Thanks again, glad i could help 🙂

Ok, I forgot to mention that all of this was done using the SaaS module manually.

Hi,

First of all, this is a great feature — thank you 🙂

I created two tenants (with separate databases) using the same username (admin) for testing purposes, and the system allowed this.

However, during authentication, only the account associated with the first created tenant can be accessed successfully. Attempts to log in with the second tenant result in the error message: "Invalid username or password."

In the AbpUsers table (Host side), two users are created with the same username but different email addresses.

According to the documentation for Shared User Accounts, username and email uniqueness should be enforced globally. However, in this case, the system allows duplicate usernames across tenants.

After a user clicks on the invitation link and chooses a username, there does not appear to be any validation preventing duplicates.

Could you please verify whether this behavior is expected, a configuration issue, or a potential bug?

This is not urgent for us, as we are not in production yet. I was just testing this functionality and wanted to share the result i got.

For reference, I have added the following in the Domain module:

Configure<AbpMultiTenancyOptions>(options =>
{
    options.IsEnabled = true;
    options.UserSharingStrategy = TenantUserSharingStrategy.Shared;
});

Thanks.

I had same issue, and fix it by removing form-select from select class.

Hi,

Thanks, I'll try it.

Hi

Here are links they've sent me for you to check:

Authenticate an IMAP, POP or SMTP connection using OAuth

How to connect to Office 365 with IMAP, Oauth2 and Client Credential Grant Flow

Thanks

Hi, from

customer’s IT administrator

Tell them it's about OAuth2 Microsoft 365

Thanks.

Thank you. Perhaps it’s best if I describe our situation so you can advise us on the best way to proceed.

We installed the application at the customer’s site and have access to a Windows Server 2016 machine and IIS. The server does not have internet access.

In order to send emails from the application, the customer’s IT administrator asked that our application be registered as a user via OAuth2 so we can send mail.

We need guidance on how to configure email OAuth2 authentication for Microsoft 365.

It seems that the AI’s “Answer A” is what we need.

What is the correct format for the callback (redirect) URL — we use all default values?