CoSecRouteMapAutoConfiguration
@AutoConfiguration(after = [WowAutoConfiguration::class], beforeName = ["me.ahoo.cosec.spring.boot.starter.pipeline.CoSecPipelineAutoConfiguration"] )
@ConditionalOnClass(name = ["me.ahoo.wow.cosec.CoSecCallerResolver", "me.ahoo.cosec.webflux.ServerWebExchanges"] )
@ConditionalOnProperty(value = ["cosec.enabled"], havingValue = "true", matchIfMissing = true)
@ConditionalOnProperty(value = ["cosec.pipeline.mode"], havingValue = "enforce", matchIfMissing = true)
The Manifest's command and service routes as the route map CoSec's pipeline reads (CoSecActions.routes), where CoSec decides the requests itself (cosec.pipeline.mode enforce, its default): a command is <context>:<command> on <aggregate>/<id>, a service route <context>:<route> on route/<route>, the names CoSecCommandAuthorizer and CoSecServiceRouteAuthorizer decide them by. It comes after the host's configuration, which defines the Manifest, and before CoSec's pipeline, whose route map file it takes the place of; an application that maps routes of its own declares its RouteMap. Experimental as wow-cosec is.
Functions
Link copied to clipboard