cap-java-auth-check
CAP Java authorization checked case by case against cds-services-bom 4.8.0 — what a WRITE grant does not cover on a bound action, and where a where-condition carries over.
Each topic is a running scenario with the observed result beside the expectation, including one the author marks as diverging: a where-condition on a bound action, long documented as ignored in Java, applies in 4.8.0 when @restrict sits on the entity and the action is named in grant. Written in Japanese.
Facts
Where it sits
Who is behind it
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer
Before choosing this
Signals
LicenceNo licenseNeither the package manifest nor the repository tree declares a licence
Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.
What it declares
Every artifact
- Type
- Sample
- Origin
- Independently maintained
- Runtime
- Java
As a sample
- Form
- does not say
Connections
Deciding who may read or change what, down to instance level
Download
README
quoted from miyasuta/cap-java-auth-check, readCAP Java 認可(Authorization)検証プロジェクト
CAP Java における認可動作の仕様を実際に検証するためのサンプルプロジェクトです。
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
History in the atlas
- First seen.
For your agent
- Ref
artifact:miyasuta-cap-java-auth-check- JSON
- /artifacts/miyasuta-cap-java-auth-check.json
- MCP
- Connecting an agent