GssApiMechanismTests: use of deprecated APIs (marked for removal)

[zzambers]

As I have been doing fixes, I have seen following warnings on JDK 24:

cryptotest/tests/SaslServerFactoryGssapiTest.java:105: warning: [removal] <T>doAs(Subject,PrivilegedAction<T>) in Subject has been deprecated and marked for removal
                Subject.doAs(subject, new PrivilegedSubjectAction(alias, props));
                       ^
  where T is a type-variable:
    T extends Object declared in method <T>doAs(Subject,PrivilegedAction<T>)
cryptotest/tests/GssApiMechanismTests.java:160: warning: [removal] <T>doAs(Subject,PrivilegedAction<T>) in Subject has been deprecated and marked for removal
            Subject.doAs(subject, new PrivilegedAction<Object>() {
                   ^
  where T is a type-variable:
    T extends Object declared in method <T>doAs(Subject,PrivilegedAction<T>)
cryptotest/tests/PolicyTests.java:71: warning: [removal] Policy in java.security has been deprecated and marked for removal
            Policy policy = Policy.getInstance(alias, null, service.getProvider());
            ^
cryptotest/tests/PolicyTests.java:71: warning: [removal] Policy in java.security has been deprecated and marked for removal
            Policy policy = Policy.getInstance(alias, null, service.getProvider());
                            ^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
5 warnings

This will probably became problem in the future.

[judovana]

Probably another reason to incorporate detections on jdk versions and cryptographic features...

[zzambers]

Detection can be done, but will again lead to reflection... (unless code is removed completely) :(