Ask - Test

Hi Jan,

Couldn't that be done with implementing a new toolkit rather?

Regards,
Zsigmond

Thanks for the hint. I thought this is somehow hardcoded because for each toolkit there are additional properties in the portal.properties. It would be nice to have a blog post with a generic example.

My main idea here was to slightly modify the existing Regex toolkit to make it more versatile.

I see. However, I think the existing toolkits have their own design and purpose. If we want to have a word list based check also, it may be better to separate its logic according to its goal. I would go for that rather than modifying the existing toolkits.

What would you like to see being covered by a blog post exactly?

Regards,
Zsigmond

I agree that word check logic could be separated into a dedicated layer.

Looking into the code I can see all this is less complex than I thought originally.

1. I was unsure how to integrate the custom password toolkit, but it seems this settings does the job (not tested yet):

passwords.toolkit=my.company.CustomToolkit

2. I thought the autogenerated passwords follow the toolkit rules, but I can see the generator only combines alphanumeric chars and stops after reaching the required length.

So I'll try to implement CustomToolkit instead, like you propose.