Upgrade to 7.1.0 breaks Studio connections - 404

Issue Description

After upgrading to 7.1.0 a customer's TIBCO Jaspersoft^® Studio connections were broken. Hitting "test connection" in the "...Access Configuration" dialog box resulted in a 404 error. Things are fine in TIBCO JasperReports^® Server. Nothing changed in terms of users.

Resolution

This customer was using a custom authentication. Unbeknownst to them, their primary url which Jaspersoft^® Studio attempts for authentication was always silently failing when they hit "test connection", but the attempt was silent because Jaspersoft Studio rolls to a secondary authentication attempt that makes use of SOAP based webservices.

The primary attempt is like:

GET /jasperserver-pro/j_spring_security_check?forceDefaultRedirect=false&j_password=superuser&j_username=superuser

Second attempt is like:

POST /jasperserver-pro/services/repository

Reviewing appserver access logs, and runtime logs it was evident the primary was erroring in 7.1.0 as well as the version prior.   In the version prior however the SOAP attempt of authentication would be fine, so the customer never new the primary problem exists.   In 7.1.0 SOAP webservices have been removed entirely.  So the secondary attempt results in the 404.   

Since SOAP no longer exists the workaround is to correct the Authentication customization so that the primary attempt works.  In this customer's case the workaround was to swap the AuthenticationProvider order in the AuthenticationManager bean so that the internal auth (DAO Provider) was first, but of course every customization is unique and different so should be corrected and owned by the customer's developers.