Unsolved
This post is more than 5 years old
202 Posts
0
12479
Data Domain local user password aging
Dear Experts!
Our customer using DD2500 with 5.7 DDOS. Customer doesnt want to change
the DD user password every time when it is expires, he want a password for the local user which doesnt expires.
The gui parameters are:
- minimum days between change
- maximum days between change
- warn before expire
- disable days after expire
Question:
Is there any option to create a non aging password for the user?
The GUI allow only to set maximum days between change and it is 99999 and it is 273 years,
but is there any other options which we can create a local user with non expiring password?
Thanks in advance!
BR:
Pal Szabo
paulo3
202 Posts
0
May 8th, 2017 05:00
Ok. I see.
Is there is any way to create a user which password doesnt expire?
for example:
- minimum days: 0
- maximum days: 1
- warn days before expire: 0
Deb_PS
156 Posts
1
May 8th, 2017 05:00
Minimum Days Between Change
The minimum number of days between password changes that you allow a user. This value must be less than the Maximum Days Between Change value minus the Warn Days Before Expire value. The default setting is 0.
Maximum Days Between Change
The maximum number of days between password changes that you allow a user. The minimum value is 1. The default value is 90.
uvetsi
19 Posts
0
May 8th, 2017 08:00
set max warning to 99999 and disable to never user add password role min-days-between-change 0 max-days-between-change 99999 warn-days-before-expire 7 disable-days-after-expire never disable-date never
paulo3
202 Posts
0
May 8th, 2017 12:00
sorry i dont understand. Cloud you write down a bit more detailed ... Thanks pal
Ruddy_SCC
6 Posts
1
May 9th, 2017 02:00
Hi,
See EMC KB 000482322 wich gives you the whole procedure to achieve your goal :
482322 : https://support.emc.com/kb/482322
kind regards,
Falc0ns1
1 Message
0
February 1st, 2022 13:00
For anyone wondering, steps 3-5 provided in the article that @RUDDY_scc shared are still relevant and work.
barry_beckers
393 Posts
0
February 7th, 2022 15:00
Why wouldn't 99999 days be good enough, instead of the default 90 days (or whatever is configured now)? That would be way long enough?
We still do that up until ddos 7.6 even running in the cloud, but I believe from a certain release you can go beyond 99999 and I even tend to set 999999, but still both options would outlive the systems actual life (and my own).
So 99999 days should do just fine.