Changing the Metadata URL during edit does not seem to affect back end

Tested in version 1.5.0-SNAPSHOT-f4a6d3c
Description
When changing the Metadata URL, it does not seem to be PUT when the edit is saved. Either that or it is not pulled from the backend to the front end, thus not impacting the Entity ID selection when the Entity ID Filter is created.

NOTE: This occurs when the user leaves the default as TRUE for the 'Initialize From Backup File?' on the Common Attributes page. The user can go back and change this to FALSE then save, then the search field responds with the correct data.
 
Steps Prerequisite: Complete Metadata Provider with Metadata URL: https://idp.unicon.net/idp/shibboleth Leave 'Initialize From Backup file' default to TRUE.

1. Log into UI
2. From Dashboard, select the Metadata Providers tab
3. Select the Edit button
4. On the Common Attributes page change the Metadata URL from
   https://idp.unicon.net/idp/shibboleth to https://signin.aws.amazon.com/static/saml-metadata.xml
5. Save the changes
6. Click the Manage Filters button
7. Click the Add Filter button
8. Type 'http' in the 'earch Criteria by Entity ID' field

What is occurring
The selection pool for the idp.unicon URL is still being accessed.
 
What is expected
The selection pool for the AWS URL should be displayed
 
Screenshot  
uniconurl
Default TRUE