Hi DGMiddlewareAccessManagement,
I don't believe simply having a top class for a user exposed this attribute even if password policy is enabled. This specific attribute (and it's value as 'TRUE') has to be added manually.
Here is an example:
Let's say the user in question is:
cn=testuser,ou=admins,o=mycompany,c=us
To mark this user with password never expires, you need to create a LDIF file as following and run dxmodify OR ldapmodify command line tool as below.
e.g. Let's call it a test.ldif and it should contain:
cn=testuser,ou=admins,o=mycompany,c=us
changetype: modify
add: dxPwdIgnoreExpired
dxPwdIgnoreExpired: TRUE
See the link I posted earlier if any doubt on dxmodify and LDIF file example.
Now from command line (assuming anonymous access is enabled to DSA):
dxmodify -h {hostname}:{port} -f test.ldif
If the DSA is locked down (with no anon access), you need to use a bind DN and password to run the above command,
dxmodify -h {hostname}:{port} -D "cn=xyz,ou=abc,o=mycompany,c=us" -w {password} -f test.ldif
NOTE: All DN values mentioned about are made up so you want to use your actual values replacing what I stated above for this to work.
I have also updated the support case that you have open with us, with same information. I put it here so others from community can benefit, if anyone has this same question.
Thanks,
Hitesh