# Special characters in AAA user gives conflicting information

**URL:** <https://dmap-community.ductus.global/t/special-characters-in-aaa-user-gives-conflicting-information/4693>\
**Category:** General\
**Created:** [May 15, 2024, 5:56am UTC](https://dmap-community.ductus.global/t/special-characters-in-aaa-user-gives-conflicting-information/4693 "2024-05-15T05:56:16Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![etappau](https://avatars.discourse-cdn.com/v4/letter/e/a9a28c/32.png) [@etappau](https://dmap-community.ductus.global/u/etappau)\
**Post date:** [May 15, 2024, 5:56am UTC](https://dmap-community.ductus.global/t/special-characters-in-aaa-user-gives-conflicting-information/4693/1 "2024-05-15T05:56:17Z")

</div>

Hi experts,

Our application vDRA is using a rather primitive version of confd 6.3, I cannot be sure if that is EoL.

However, our customer is reporting a very unique problem.

If I were to setup a cli user with special characters in password like XXXX!X{[UV-], it cannot display the committed changes.

paul@orchestrator[drm01v]# show configuration commit changes 0  
!  
! Created by: admin  
! Date: 2024-05-14 16:13:12  
! Client: cli  
!  
% No configuration changes found.  
paul@orchestrator[drm01v]# exit  
Connection to localhost closed.  
cps@drm01v:~$ cli  
admin@localhost’s password:  
Welcome to the CPS CLI  
admin connected from 172.17.0.1 using ssh on orchestrator  
admin@orchestrator[drm01v]# show configuration commit changes 0  
!  
! Created by: admin  
! Date: 2024-05-14 16:13:12  
! Client: cli  
!  
aaa authentication users user paul  
uid 9000  
gid 100  
password $1$DMExUlAA$E7eFu5UgP.nKQNdo8PGkW0  
ssh\_keydir “”  
homedir “”  
!  
admin@orchestrator[drm01v]# show confd-state version  
confd-state version 6.3

Has anyone experienced this issue in their deployments?

Any leads will be most appreciated.

Thanks,

Paul

---

<div class="post-metadata">

**Author:** ![cohult](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/cohult/32/221_2.png) [@cohult](https://dmap-community.ductus.global/u/cohult)\
**Post date:** [May 15, 2024, 12:09pm UTC](https://dmap-community.ductus.global/t/special-characters-in-aaa-user-gives-conflicting-information/4693/2 "2024-05-15T12:09:52Z")

</div>

Hi, can’t reproduce with a modern ConfD version.

Regarding 6.3 EOL:

- 6.3 - released 22 Nov 2016.
- End of Maintenance Date - 1 Dec 2018.
- End of Support Date - 1 Dec 2019.

---

<div class="post-metadata">

**Author:** ![etappau](https://avatars.discourse-cdn.com/v4/letter/e/a9a28c/32.png) [@etappau](https://dmap-community.ductus.global/u/etappau)\
**Post date:** [May 15, 2024, 12:21pm UTC](https://dmap-community.ductus.global/t/special-characters-in-aaa-user-gives-conflicting-information/4693/3 "2024-05-15T12:21:50Z")

</div>

Thanks for your response.  
Are there any general guidelines for using passwords for aaa user in 6.3?  
I couldn’t seem to find any.

Regards,  
Paul

---

<div class="post-metadata">

**Author:** ![cohult](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/cohult/32/221_2.png) [@cohult](https://dmap-community.ductus.global/u/cohult)\
**Post date:** [May 15, 2024, 12:37pm UTC](https://dmap-community.ductus.global/t/special-characters-in-aaa-user-gives-conflicting-information/4693/4 "2024-05-15T12:37:39Z")

</div>

Not that I can remember going back eight years in the memorydex 🙂

---

<div class="post-metadata">

**Author:** ![etappau](https://avatars.discourse-cdn.com/v4/letter/e/a9a28c/32.png) [@etappau](https://dmap-community.ductus.global/u/etappau)\
**Post date:** [May 15, 2024, 1:11pm UTC](https://dmap-community.ductus.global/t/special-characters-in-aaa-user-gives-conflicting-information/4693/5 "2024-05-15T13:11:38Z")

</div>

Thanks.  
Please can you share what version of confD did you test this on?  
Also, what’s the next release for 6.3?  
Is that EoL as well.  
I wanted to know what is the next best version that will not have this defect.

Your response will be appreciated.

Regards,  
Paul

---

<div class="post-metadata">

**Author:** ![cohult](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/cohult/32/221_2.png) [@cohult](https://dmap-community.ductus.global/u/cohult)\
**Post date:** [May 16, 2024, 7:41am UTC](https://dmap-community.ductus.global/t/special-characters-in-aaa-user-gives-conflicting-information/4693/6 "2024-05-16T07:41:13Z")

</div>

Hi,

> [@etappau](#):
>
> Please can you share what version of confD did you test this on?

```plaintext
# show confd-state version
confd-state version 8.0.14
# config
Entering configuration mode terminal
(config)# show configuration commit changes  
% no rollback files found
(config)# aaa authentication users user admin change-password 
Possible completions:
  confirm-password Confirm New password
  new-password New password
  old-password Old password
(config)# aaa authentication users user admin change-password              
Value for 'old-password' (<string>): *****
Value for 'new-password' (<string>): ************ 
Value for 'confirm-password' (<string>): ************ 
(config)# 
System message at 2024-05-16 09:28:02...
Commit performed by system via system using system.
(config)# show configuration commit changes 0
!
! Created by: system
! Date: 2024-05-16 09:28:02
! Client: system
!
aaa authentication users user admin
 password $1$MELDf9/q$dA9F295dt29IbJppFJdeD0
!

```

> [@etappau](#):
>
> Also, what’s the next release for 6.3?  
> Is that EoL as well.  
> I wanted to know what is the next best version that will not have this defect.

> [@ConfD Premium no longer available? Future of ConfD?](http://dmap-community.ductus.global/t/confd-premium-no-longer-available-future-of-confd/4552/2):
>
> Your first sentence answers the question which you are asking. ConfD Basic 8.0.x is the last branch being released. ConfD Basic should not be used for new projects. ConfD Basic will be going away.

You should check with your ConfD support contacts.

Best regards