2021/6/29 5:17:39 -0700, anika.westb...@raytion.com:
> Dear Developers,
>
> we have the problem with Kerberos and AdoptOpenJDK in a cross-realm
> setup that the first request succeeds, but subsequent requests
> fail. The reason is that the ticket from the referrals cache does not
> work for proxy
On Wed, 30 Jun 2021 15:45:25 GMT, Weijun Wang wrote:
>> Add a cache to record which sources have called `System::setSecurityManager`
>> and only print out warning lines once for each.
>
> Weijun Wang has updated the pull request incrementally with one additional
> commit since the last revision
Dear Developers,
we have the problem with Kerberos and AdoptOpenJDK in a cross-realm setup that
the first request succeeds, but subsequent requests fail. The reason is that
the ticket from the referrals cache does not work for proxy requests. We opened
this ticket:
https://github.com/adoptium/a
> Add a cache to record which sources have called `System::setSecurityManager`
> and only print out warning lines once for each.
Weijun Wang has updated the pull request incrementally with one additional
commit since the last revision:
update cache key from String to Class
-
Cha
On Wed, 30 Jun 2021 06:32:04 GMT, Alan Bateman wrote:
>> I hope this is uncommon but if that class is loaded by a `ClassLoader` again
>> and again then it will be different each time. I'll investigate more.
>
> WeakHashMap, Boolean>, where the key is the caller, should be okay
> (assume synchro
On Wed, 30 Jun 2021 11:49:51 GMT, Сергей Цыпанов
wrote:
>> In some JDK classes there's still the following hashCode() implementation:
>>
>> long objNum;
>>
>> public int hashCode() {
>> return (int) objNum;
>> }
>>
>> This outdated expression should be replaced with Long.hashCode(long) as
> In some JDK classes there's still the following hashCode() implementation:
>
> long objNum;
>
> public int hashCode() {
> return (int) objNum;
> }
>
> This outdated expression should be replaced with Long.hashCode(long) as it
>
> - uses all bits of the original value, does not discard any
A draft Authorization implementation, untested.
--
Regards,
Peter Firmstone
/**
* Authorization class, instances contain the domains and Subject of the
* Authorization context, used for Authorization decisions by Guard
* implementations. Provides static utility methods to make
privilged
On 30/06/2021 08:19, Bernd Eckenfels wrote:
Hello, sorry for being unpopular, but I just hate it to waste
developer resources,
I realy think this deprecation message should be re-considered, it
broke a lot of things, the amount of work to implement a caching
solution feels like a waste of tim
Hello, sorry for being unpopular, but I just hate it to waste developer
resources,
I realy think this deprecation message should be re-considered, it broke a lot
of things, the amount of work to implement a caching solution feels like a
waste of time and on top of it, there is no clear replacem
10 matches
Mail list logo
