The new update disables any possibility to use managed challenges with or without tag scope - the client always says he has no right to use managed challenges - hubservice-log:
2026-08-27 16:56:41.762 +02:00 [WRN] Certify.Server.Hub.Api.Services.ManagedChallengeScopeService Managed challenge access denied for principal 69ed00a2-a6bb-4720-87d8-cdaa494bfea2: no authorizing role grants 7dc15feb-0014-4ee6-baa6-809a59038537 (scoped assigned roles: (none))
2026-08-27 16:56:41.762 +02:00 [WRN] Certify.Server.Hub.Api.Controllers.ManagedChallengeController ValidateManagedInstanceChallengeAccessAsync found no accessible managed challenge for managed instance 85e6bf51-c9fe-4ad0-a0a3-323c086a70d3 / security principal 69ed00a2-a6bb-4720-87d8-cdaa494bfea2: Security principal is not authorised to use managed challenges
2026-08-27 16:56:41.762 +02:00 [WRN] Certify.Server.Hub.Api.Controllers.ManagedChallengeController AuthorizeManagedChallengeActionAsync managed-instance authorization failed for action managedchallenge_cleanup_action, managed cert , identifier owa.domain.tld, challenge type dns-01: Managed instance is not permitted to access a matching managed challenge for this request.
2026-08-27 16:56:41.763 +02:00 [WRN] Certify.Server.Hub.Api.Controllers.ManagedChallengeController AuthorizeManagedChallengeActionAsync denied by managed-instance authorization for action managedchallenge_cleanup_action, managed cert , identifier owa.domain.tld, challenge type dns-01: Managed instance is not permitted to access a matching managed challenge for this request.
i think there is a bug in roles for security principals - working permission settings from 7.1.1 are no longer working right now (managed challenge with tag, managed challenge consumer with tag scope filter)
I found the new setting for the hub to enable untagged challenges for tag settings but enabling/disabling that has no effect.
The new update disables any possibility to use managed challenges with or without tag scope - the client always says he has no right to use managed challenges - hubservice-log:
2026-08-27 16:56:41.762 +02:00 [WRN] Certify.Server.Hub.Api.Services.ManagedChallengeScopeService Managed challenge access denied for principal 69ed00a2-a6bb-4720-87d8-cdaa494bfea2: no authorizing role grants 7dc15feb-0014-4ee6-baa6-809a59038537 (scoped assigned roles: (none))
2026-08-27 16:56:41.762 +02:00 [WRN] Certify.Server.Hub.Api.Controllers.ManagedChallengeController ValidateManagedInstanceChallengeAccessAsync found no accessible managed challenge for managed instance 85e6bf51-c9fe-4ad0-a0a3-323c086a70d3 / security principal 69ed00a2-a6bb-4720-87d8-cdaa494bfea2: Security principal is not authorised to use managed challenges
2026-08-27 16:56:41.762 +02:00 [WRN] Certify.Server.Hub.Api.Controllers.ManagedChallengeController AuthorizeManagedChallengeActionAsync managed-instance authorization failed for action managedchallenge_cleanup_action, managed cert , identifier owa.domain.tld, challenge type dns-01: Managed instance is not permitted to access a matching managed challenge for this request.
2026-08-27 16:56:41.763 +02:00 [WRN] Certify.Server.Hub.Api.Controllers.ManagedChallengeController AuthorizeManagedChallengeActionAsync denied by managed-instance authorization for action managedchallenge_cleanup_action, managed cert , identifier owa.domain.tld, challenge type dns-01: Managed instance is not permitted to access a matching managed challenge for this request.
i think there is a bug in roles for security principals - working permission settings from 7.1.1 are no longer working right now (managed challenge with tag, managed challenge consumer with tag scope filter)
I found the new setting for the hub to enable untagged challenges for tag settings but enabling/disabling that has no effect.