Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(jans-cedarling): support having types in the Cedar resource param #10538

Open
rmarinn opened this issue Jan 2, 2025 · 0 comments
Open
Labels
comp-jans-cedarling Touching folder /jans-cedarling enhancement kind-feature Issue or PR is a new feature request

Comments

@rmarinn
Copy link
Contributor

rmarinn commented Jan 2, 2025

Is your feature request related to a problem? Please describe.

Cedarling does not support having types in a Resource. So an HTTP_Request entity defined below cannot be used as a Cedar Resource:

namespace Jans {
    type Url = { "host": String, "path": String, "protocol": String };
    entity HTTP_Request = {
        "url": Url
   };
}

Cedarling return an error like
ResourceEntity(Create(CreateRecord("Jans::Url", MissingClaim("path"))))
when a resource like

{
    "url": "https://some-iss/.well-known/openid-configuration"
}

is given. Since Cedarling doesn't know how to map from string -> Url in the resource.

Describe the solution you'd like

...

Describe alternatives you've considered

...

Additional context

...

@rmarinn rmarinn added comp-jans-cedarling Touching folder /jans-cedarling enhancement labels Jan 2, 2025
@mo-auto mo-auto added the kind-feature Issue or PR is a new feature request label Jan 2, 2025
@rmarinn rmarinn changed the title feat(jans-cedarling): support having types and entities in the Cedar resource param feat(jans-cedarling): support having types in the Cedar resource param Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp-jans-cedarling Touching folder /jans-cedarling enhancement kind-feature Issue or PR is a new feature request
Projects
None yet
Development

No branches or pull requests

3 participants