#50691 Create SSHA512 type in password_plugins module
Closed: wontfix by aborah. Opened by aborah.

Issue Description

Create SSHA512 type in password_plugins module

Package Version and Platform

All


Uhhh ... why? It's enabled by default in all server versions, so there is no need for this plugin module to exist? The pbkdf2 module only needs to exist for upgrading configurations or instances that had pbkdf2 disabled in a specific version.

Basically what are you trying to achieve?

Metadata Update from @firstyear:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

I was working on a script which requires to access SSHA512, i was thinking if we can import it directly like

from lib389.password_plugins import SSHA512Plugin

SSHA512Plugin(topo.standalone).disable()

SSHA512Plugin(topo.standalone).status()

it will make it short and easy to access .

Yeah but why do you need to disable it?

Actually i need to delete it ,

SSHA512Plugin(topo.standalone).delete()

and try to restart DS . which should fail as

DS should not started without mandatory SSHA512 plugin

This is part of my Test case (as the _protected = True , i will not be able to delete it . :( )

And i was thinking as i was going though this part , why dont make a type of SSHA512 to make it easy and short access

It should be like 3 lines, just add this module when you submit the test case? I don't think it needs it's own ticket ...

ok , greate . will close this one

Metadata Update from @aborah:
- Issue close_status updated to: worksforme
- Issue status updated to: Closed (was: Open)

Any way , are there any way to delete this SSHA512 plugin for testing purpose ??

SSHA512Plugin(topo.standalone).delete()

This one will not work , as _protected = True

ssha512plug = SSHA512Plugin(topo.standalone)
ssha512plug._protected = False
ssh1512plug.delete()

One day I hope you learn you don't need to make everything one line of code to do every action, sometimes assign variables ike above helps you see solutions to problems ;)

This works , thanks .

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3746

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: worksforme)

Metadata