Add graalvm reachability metadata to sso service

[gbaso]

Describe the feature

Add reachability metadata for service sso, namely for the constructor of SsoProfileCredentialsProviderFactory.

Use Case

GraalVM native image requires reflection hints for code that is only used by reflection.

Proposed Solution

Add a file reflect-config.json under src/main/resources/META-INF/native-image/software.amazon.awssdk/sso with:

[
  {
    "name": "software.amazon.awssdk.services.sso.auth.SsoProfileCredentialsProviderFactory",
    "methods": [
      {
        "name": "<init>",
        "parameterTypes": []
      }
    ]
  }
]

Other Information

Native hints can be provided by the application (e.g., for spring applications, via @ImportRuntimeHints), but it's mostly a try-and-error process. Libraries providing metadata simplify the operation of building a native image considerably.

Other aws services already provide metadata, see ssooidc.

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

AWS Java SDK version used

2.29.52

JDK version used

21.0.5

Operating System and version

MacOS 15.2

[debora-ito]

@gbaso Sorry for the long delay in replying. Taking a look at the PR.

[scrocquesel]

@debora-ito not related to the OP PR, but he mentions that sso oidc reachability was done long ago. The issue is that the referenced class software.amazon.awssdk.services.ssooidc.SsoOidcTokenProviderFactory has never existed. I think there is a typo with SsoOidcProfileTokenProviderFactory.

[debora-ito]

@scrocquesel good catch 🤦🏻‍♀️ thank you!

@gbaso would you mind fixing ssooidc/reflect-config.json in your PR?

[gbaso]

@debora-ito sure, I'll fix it now.

[scrocquesel]

I have fixed this issue with GraalVM substitution in the Quarkus extension and we faced another issue. Both providers make use of a static field which is statically initialized with a call to userHomeDirectory().
This call is evaluated during native image build to empty string, providers will never find the cached token.
To resolve this, either add a GraalVM feature to specify those two classes need to be runtime initialized, let the field be an instance field or lazy initialize it.