Authorization layer API and low level access checks.

[Dalibor Topic]

Hi Peter,

Larger changes, such as those that appear to be proposed here, should 
come with their own JEP. Please see 
https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html for details.

JEPs help among other things build consensus around ideas. Typically it 
takes around 6 months from the inception of a release, until the feature 
set is complete, so that should give you some sense of the timings involved.

It can also be useful to split larger proposed changes into several 
conceptually distinguished smaller ones, and to build up consensus 
gradually that way.

cheers,
dalibor topic

On 25.06.2021 07:59, Peter Firmstone wrote:
> Thanks Dalibor,
> 
> Would targeting Java 18 be practical?
> 
> Also it won't take long to code a prototype, just not sure of the process.
> 
> Cheers,
> 
> Peter.
> 
> 
> On 24/06/2021 9:30 pm, Dalibor Topic wrote:
>> On 24.06.2021 04:24, Peter Firmstone wrote:
>>> Thanks Andrew,
>>>
>>> For the simple case, of replacing the SecurityManager stack walk, one 
>>> could use reflection.
>>>
>>> Thank you for also confirming that is not possible (or at least very 
>>> unlikely) to add a GuardBuilder to Java 8, the proposal is for JDK 
>>> code to use a provider mechanism, to intercept permission checks, so 
>>> custom authentication layers can be implemented, this could be 
>>> accepted in future versions of Java, but not existing. As it is said, 
>>> there is no harm in asking.
>>
>> Generally speaking, adding any public APIs to a platform release after 
>> its specification has been published, is always going to be a very 
>> tall order involving the JCP, among other things. It's not really 
>> worth it, when other technical solutions, such as multi-release JARs, 
>> already exist, that alleviate the necessity.
>>
>> cheers,
>> dalibor topic
>>

-- 
<http://www.oracle.com> Dalibor Topic
Consulting Product Manager
Phone: +494089091214 <tel:+494089091214>, Mobile: +491737185961
<tel:+491737185961>, Video: dalibor.topic at oracle.com
<sip:dalibor.topic at oracle.com>

Oracle Global Services Germany GmbH
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRB 246209
Geschäftsführer: Ralf Herrmann