Provide instructions for getting application working with Okta about spring-boot-security-saml-sample

[mraible]

I figured out how to do it! http://stackoverflow.com/a/27787545/65681

[vdenotaris]

Hi. I'm sorry but I have to reject your pull request because it doesn't provide relevant improvements.

• the use of a .properties file (instead of a .xml) is yet compliant with the Log4j Spring Boot Starter;
• it is possible to manage all Spring-core dependencies by using a Maven BOM called Spring Platform (see http://platform.spring.io/platform/);
• your pull request contains IDE-related metadata that makes the code dirty.

Furthermore, this project represents a general-purpose solution. It is preferable to create specific forks in order to properly integrate third-party frameworks (like Okta).

Thank you anyway for your contribution and attention.
Cheers, Vi.

[mraible]

• Yes, but I changed to use the Log4j2 starter and this requires a log4j2.xml file.
• Yes, but Spring Boot seems to recommend using its parent over the Spring Platform BOM. http://projects.spring.io/spring-boot/#quick-start Also, you can't manage plugin versions and information with a BOM import.
• It's only in the .gitignore file. The current one has an ignore for "Mobile Tools for Java (J2ME)", which seems irrelevant as well.

[mraible]

Using Spring Boot as a parent also eliminates these warnings on startup:

$ mvn spring-boot:run
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for com.vdenotaris.spring:spring-boot-security-saml-sample:war:1.0.0.RELEASE
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 133, column 12
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-war-plugin is missing. @ line 127, column 12
[WARNING] 'build.plugins.plugin.version' for org.springframework.boot:spring-boot-maven-plugin is missing. @ line 118, column 12
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.