#6785 [TESTS] Provide an integration test suite for user short name feature
Opened 3 years ago by mbabinsk. Modified 2 years ago

The suite(s) should test the following scenarios regarding short name authentication in indirect AD integration scenario:

Basic CRUD:

  • adding/removing domains from DRO (pass)
  • adding empty DRO (pass)
  • adding non-existent domains to DRO (error)
  • adding removed AD domain to DRO (error)
  • adding disabled AD domain to DRO (error)

Logins:

  • set the global domain resolution order to IPA and Ad domains and verify all users can login with short names
  • remove an AD domain from global DRO and verify all users except those from removed domain can login w/ short names
  • remove an IPA domain from DRO and verify that no IPA users can login w/ short name
  • depending on SSSD implementation, set global DRO to empty value and see what happens (either revert to default behavior or enforce fully qualified names for all users_

Then test also the interplay between global and view-specific DRO:

  • set all domains in global config, set only one domain on view, apply view on the client, verify that only the DRO from view is applied
  • set an IPA domain in global DRO, set AD domains in view-specific DRO, verify that only the AD users can now use short names to login when the view is applied

More test cases may be added when necessary.


Metadata Update from @pvoborni:
- Issue set to the milestone: FreeIPA 4.5.1

3 years ago

Metadata Update from @pvoborni:
- Issue priority set to: major

3 years ago

Metadata Update from @mbasti:
- Issue set to the milestone: FreeIPA 4.5.2 (was: FreeIPA 4.5.1)

3 years ago

FreeIPA 4.5.1 has been released, moving to FreeIPA 4.5.2 milestone

Metadata Update from @tkrizek:
- Issue set to the milestone: FreeIPA 4.5.3 (was: FreeIPA 4.5.2)

2 years ago

Metadata Update from @tkrizek:
- Issue set to the milestone: FreeIPA 4.5.4 (was: FreeIPA 4.5.3)

2 years ago

Metadata Update from @tkrizek:
- Issue set to the milestone: FreeIPA 4.5.5 (was: FreeIPA 4.5.4)

2 years ago

Login to comment on this ticket.

Metadata