Project

General

Profile

Actions

Defect #1450

closed

It is not possible to register with username not defined in EAV

Added by Ondřej Kopr over 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
High
Assignee:
Roman Kučera
Target version:
Start date:
01/15/2019
Due date:
% Done:

100%

Estimated time:
Affected versions:
Owner:

Description

This bug has probably some connection with: #1449

There is workaround define attribute with username code for contract, tree node or etc. and then registration works.

Affected version: 2.1.0


Related issues

Related to password-reset - Defect #1400: Public page for reset password cannot be openedNewPeter Štrunc12/05/2018

Actions
Actions #1

Updated by Peter Štrunc over 5 years ago

This is not defect. You either need to specify login generator and mark username eav as read-only (which will result in this attribute not showing in registration form), or you let user choose their username by letting them fill it in the form. But you always must specify username somehow.

Actions #2

Updated by Radek Tomiška over 5 years ago

I doesn't agree, some default behavior should be defined and application should work as default. The same as #1400.

Actions #3

Updated by Radek Tomiška over 5 years ago

  • Related to Defect #1400: Public page for reset password cannot be opened added
Actions #4

Updated by Peter Štrunc over 5 years ago

Default behavior after module instalation is username showing in registration form. If you delete the required attribute from configuration and then complain that it does not work, then i cant really do much.

Actions #5

Updated by Ondřej Kopr over 5 years ago

Use cases:

1) username is generated by default generators in Reg module. Username does not have to be defined in EAV. It is useless attribute that will be show in eavs.
2) username is generated by generators in core module. Username does not have to be defined in EAV. It is also useless attribute that will be show in eavs.

Some existing project that use reg module doesn't defined username in eaves. The project/s is still not upgradable to newer version.

Now exists bigger problem defined in #1449 this ticket is minor problem that can be solved by override service DefaultRegIdentityService. But the method in ticket #1449 can search attributes in different formDefinition.

Actions #6

Updated by Marcel Poul about 5 years ago

  • Subject changed from Is not possible self registrate without defined username in EAV to It is not possible to register with username not defined in EAV
Actions #7

Updated by Ondřej Kopr over 4 years ago

  • Assignee changed from Peter Štrunc to Ondřej Kopr
  • Priority changed from Normal to High
Actions #9

Updated by Ondřej Kopr over 4 years ago

  • Status changed from New to In Progress
Actions #10

Updated by Ondřej Kopr over 4 years ago

  • Status changed from In Progress to Needs feedback
  • % Done changed from 0 to 90

New configuration property was implemented. Tests are included. I was little bit stuck on tests with generator.

Documentation: https://wiki.czechidm.com/devel/documentation/modules_reg#configuration

Commit: https://git.bcvsolutions.eu/modules/reg/commit/bbe3345cae0ef0896e88fa41e9f62a2fc0ad3c77 (branch: develop)

Actions #11

Updated by Ondřej Kopr over 4 years ago

  • Target version set to 2.3.0
Actions #12

Updated by Roman Kučera over 4 years ago

  • Status changed from Needs feedback to Resolved
  • Assignee changed from Ondřej Kopr to Roman Kučera
  • % Done changed from 90 to 100

Thx for implementation.
I did review and works as intended.

Actions #13

Updated by Roman Kučera over 4 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF