[GH-ISSUE #2451] Unable to add multiple aliases at once to a user #1234

Closed
opened 2026-03-02 13:42:36 +03:00 by kerem · 2 comments
Owner

Originally created by @SGeeves on GitHub (May 15, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2451

Description

Within Identity -> Admin -> Users
We are unable to add more than one alias at a time. The 'Add Aliases' box advises to put 'One per line' however this doesn't work and shows the below error.

We've failed to create the Aliases: Invalid value specified for property 'mail' of resource 'User'.

*Adding a single alias works without issue here.

I am a sponsor under: FutureITNZ

Environment data

Sponsored instance 
Front end version number: 5.6.2
Back end version number: 5.6.3
Tried Tenant Cache Clear: false 
Tried Token Cache Clear: false
Originally created by @SGeeves on GitHub (May 15, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2451 ### Description Within Identity -> Admin -> Users We are unable to add more than one alias at a time. The 'Add Aliases' box advises to put 'One per line' however this doesn't work and shows the below error. We've failed to create the Aliases: Invalid value specified for property 'mail' of resource 'User'. *Adding a single alias works without issue here. I am a sponsor under: FutureITNZ ### Environment data ```PowerShell Sponsored instance Front end version number: 5.6.2 Back end version number: 5.6.3 Tried Tenant Cache Clear: false Tried Token Cache Clear: false ```
kerem 2026-03-02 13:42:36 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (May 15, 2024):

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug."

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

<!-- gh-comment-id:2111443134 --> @github-actions[bot] commented on GitHub (May 15, 2024): Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/ If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug." Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
Author
Owner

@JohnDuprey commented on GitHub (May 15, 2024):

Thanks for the report, this is fixed in dev and will be in the next release.

<!-- gh-comment-id:2112673745 --> @JohnDuprey commented on GitHub (May 15, 2024): Thanks for the report, this is fixed in dev and will be in the next release.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#1234
No description provided.