Skip to content

CAS registered service does not match service URLs with explicit port #6

@kahoona77

Description

@kahoona77

The operator generates CAS registered services with a serviceId pattern that expects the service path directly after the host.
Example:

"serviceId": "^https://dev1[.]k3ces[.]localdomain/scm(/.*)?$"

However, CAS may receive service URLs with an explicit port:
https://dev1.k3ces.localdomain:443/scm/api/v2/cas/auth/...
This does not match the generated pattern, causing CAS to reject the login with:

Service is not registered in the service registry
registered service is [Optional.empty]
HTTP 403

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions