[GH-ISSUE #3026] NinjaRMM Custom Field Device Link adding an extra "\device" to end of string causing broken link #1503

Closed
opened 2026-03-02 13:44:46 +03:00 by kerem · 3 comments
Owner

Originally created by @DavidHGAK on GitHub (Dec 28, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3026

Description

We integrated NinjaRMM into CIPP for the convenient O365 tenant links we get in the custom fields tab. To view LAPS passwords we were hoping to click the Device Entra link but it generates a link like below with an extra "/deviceId" at the end:

https://entra.microsoft.com/tenant.com/#view/Microsoft_AAD_Devices/DeviceDetailsMenuBlade/~/Properties/deviceId/xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx/deviceId/

Notice at the end of the string is a 2nd "/deviceId" which seems to break the link. If I remove the 2nd "/deviceiD" manually from the end it points to the device's Entra page like we want!

It looks like it just needs to somehow generate these custom links without that ending.

Environment data

We use a hosted CIPP instance and do not self-host.
Originally created by @DavidHGAK on GitHub (Dec 28, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3026 ### Description We integrated NinjaRMM into CIPP for the convenient O365 tenant links we get in the custom fields tab. To view LAPS passwords we were hoping to click the Device Entra link but it generates a link like below with an extra "/deviceId" at the end: https://entra.microsoft.com/tenant.com/#view/Microsoft_AAD_Devices/DeviceDetailsMenuBlade/~/Properties/deviceId/xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxx/deviceId/ Notice at the end of the string is a 2nd "/deviceId" which seems to break the link. If I remove the 2nd "/deviceiD" manually from the end it points to the device's Entra page like we want! It looks like it just needs to somehow generate these custom links without that ending. ### Environment data ```PowerShell We use a hosted CIPP instance and do not self-host. ```
kerem 2026-03-02 13:44:46 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Dec 28, 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:2564130922 --> @github-actions[bot] commented on GitHub (Dec 28, 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

@MWG-Logan commented on GitHub (Dec 30, 2024):

Please note my changes have only been committed to the interface-rewrite branch. If it gets merged, you'd probably need to wait until the rewrite goes prod.

<!-- gh-comment-id:2565915845 --> @MWG-Logan commented on GitHub (Dec 30, 2024): Please note my changes have only been committed to the `interface-rewrite` branch. If it gets merged, you'd probably need to wait until the rewrite goes prod.
Author
Owner

@KelvinTegelaar commented on GitHub (Jan 2, 2025):

Solved in beta! :)

<!-- gh-comment-id:2568003172 --> @KelvinTegelaar commented on GitHub (Jan 2, 2025): Solved in beta! :)
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#1503
No description provided.