Not reading azure.activedirectory properties from Spring Property file passed by -Dspring.config.location=<property file>

[prabdeb]

Environment

• Spring boot starter:

  • active directory spring boot starter

• OS Type: Linux

• Java version:

  • 1.8

Summary

No reading azure.activedirectory properties (Ex. azure.activedirectory.tenant-id) from Spring Property file passed by -Dspring.config.location=<property file> in Java Command line while starting the application

Reproduce steps

Do not hard code azure.activedirectory.* properties in a file application.properties instead have them in a property file, created in a location other than classpath and passed to JVM using Spring Option - -Dspring.config.location=<property file>

Expected Results

Should read the properties from a file that is not in classpath and loaded via Spring Option

Actual Results

Receiving exception - azure.activedirectory.tenant-id not found

Workaround

Instead of passing -Dspring.config.location=<property file> in Java Command Line while starting application, rename the <property file> into application.properties and place into the same directory from where the Java Command Line is triggered to start the application - Ex.

cp $PROPERTY_FILE_PATH /home/user/application.properties && cd /home/user && java -jar application.war

[saragluna]

Thanks for reaching out. Is the issue #927 related to this one? Just trying to figure out your using case. And we'll look into this issue.

[prabdeb]

@saragluna No this two issues are separate. Thanks for considering this issue!

[chenrujun]

Hi, @prabdeb .

I can not reproduce you problem in my localhost with our sample app.

Here is the screenshot:

1. Which version are you using?
2. Could you please try to use the sample app to reproduce your problem?

[prabdeb]

Yes @chenrujun the application is starting without any error, but while trying to access the API we getting 403 forbidden error, where the bearer token is correct only.

However if we do this cp $PROPERTY_FILE_PATH /home/user/application.properties && cd /home/user && java -jar application.war then the authentication is working properly

EDIT: One interesting observation is that if the property file passed via --spring.config.location= does have extension as .properties this works, but if the property file does not have extension .properties this will not work.

For example property file abc.properties will work and abc-properties will not work.

And for our use case since we are reading from Azure Key Vault, there we can not store any secret file with . in name - reference

cc: @salujamanish

[chenrujun]

@prabdeb .

if the property file does not have extension .properties this will not work

Yes, that is the root cause. It has already been discussed in stackoverflow.

And I find related code in spring boot.

And for our use case since we are reading from Azure Key Vault, there we can not store any secret file with . in name

Could you please save abc in Key Vault, and rename to abc.properties when use it?

i.e.
change

cp $PROPERTY_FILE_PATH /home/user/application.properties && cd /home/user && java -jar application.war

to

mv $PROPERTY_FILE_PATH ${PROPERTY_FILE_PATH}.properties && \
java -Dspring.config.location=${PROPERTY_FILE_PATH}.properties -jar /home/user/application.war

[chenrujun]

I'll close this issues because it's caused by spring framework restriction, not by our starter module.

[scgbear]

Internal Tracking

CSEF368746

[philwebb]

To help with this, as of Spring Boot 2.4.0-M3 you can import extensionless files by using an extension hint. See spring-projects/spring-boot#22280 for details.

[chenrujun]

@philwebb Thank you for your information.