Activities of "mkinc"

Thanks. We'll test Email confirmed, IsExternal, Creation date and Modified date filters when there's a non-RC 7.3 version.

Do you have a time frame for which you'd expect to get back to me on this? Thanks.

OK. Is there an update on this?

Thanks Nico.

We'll try updating to 7.3 when it's not in preview and let you know if we have any issues with the behaviour.

Matt

Thanks. When can I expect to hear about this? Can we get the question back for this?

Hi. Has this support been missed off? Also, please can I get the question refunded. Is this the correct way of raising bugs by the way? Thanks.

• ABP Framework version: v7.3.0 - replicable on ABP demo on 24th May 2023.
• UI type: Angular
• DB provider: Unknown
• Tiered (MVC) or Identity Server Separated (Angular): Unknown
• Steps to reproduce the issue:
  • Login as admin
  • Navigate to Administration -> Identity Management -> Users
    • Observe all users shown in table.
  • Show the Advanced filters
  • Set 'Email confirmed' to on and click 'Refresh'
    • Observe no users correctly displayed
  • Set 'Email confirmed' to off and click 'Refresh'
• Expected behaviour: All users shown again.
• Actual behaviour: No users shown (and not even 'No data available' label)
• Further issues:
  • Same is replicable when using 'Is external'.
  • Issue not rectified when clicking 'Clear'.
  • Filtering by Creation date or Modified date does not appear to work at all (all users always displayed regardless of what creation date or Modified date range is used).

• ABP Framework version: v7.2.1
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): Separated AuthServer
• Steps to reproduce the issue:
  • Create user, enabling the 'Should change password on next login'.
  • Login as user
  • When prompted for new password, use the original password for current, new and new (repeat)
• Expected behaviour: Error on submit / validation error that doesn't allow submit.
• Actual behaviour: Password is allowed and user is logged in.

I can't really see any justification to suggest this isn't a bug since forcing a user to change password on next login is something used for security. Untested: Does this affect the 'Force users to periodically change password' feature as well?

Hi maliming,

Thanks, we were using 7.1.1. I've upgraded to 7.2.1 and can see the feature which should work in our favour. We'll add some custom code to send the email.

It would be a great feature to have some sort of 'Invite user' action in user administration area AND 'Invite user' checkbox on user creation as part of the template.

Cheers,

Matt

• ABP Framework version: v7.1
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): Identity server separated

Is there any out of the box solution for any of the following:

Option A:

1. Admin creates user under a specific tenancy (optionally with user changes password on login)
2. User is emailed to say an account is created for them including their password.

Option B:

1. Admin creates user under a specific tenancy (optionally with user changes password on login)
2. Admin can click a button to invite that user to login to the system.

Option C:

1. Admin sets up an email address domain for which users can create accounts.
2. User can self register. If the email address domain used matches a domain relating to a tenant, it allows the registration, otherwise it does not allow the registration.

I did think the flow could be that the user is given a link to the 'Forgot password' page and goes through that flow, but this isn't very professional in my opinion. It seems strange that the out of the box solution is that anybody can create a user under any tenancy.

Thanks!