M
Michael Jacobs
Guest
The appSecurity*.xml files are 90% pure Spring. About 5% is OE extensions to inject CORS support and AppServer SSO conversion to Client-Principal. Another 2% is a Spring compliant provider for the OERealm support. The last 3% is subclassed Spring objects that respond with JSON payloads for authn success, failure, and invalid sessions for JavaScript (JSDO) clients when they accept the type application/json. Even the OE written Spring beans conform to Spring's framework and configuration file schema. It's all there in the Spring documentation if one has a requirement for handling special use-cases and intestinal fortitude to dig into the how and why. General statement: Anything OE written in the appSecurity configurations "should" have documentation that describes its purpose, relationship to Spring security processes, and its configuration options. I guess filling in the blanks is why this forum exists. Continue asking - I'll continue helping you have fun with your new toys. Mike J.
Continue reading...
Continue reading...