This only affects EZID.
- Alter credentials to be invalid so that id cannot be registered on dataset create (simulates service unavailable)
- Create dataset
- Restore credentials
- Publish dataset, see error about being unable to contact remote service in UI but log indicates identifier does not exist:
[2017-05-31T11:11:14.608-0400] [glassfish 4.1] [WARNING] [] [edu.harvard.iq.dataverse.DOIEZIdServiceBean] [tid: _ThreadID=50 _ThreadName=jk-connector(1)] [timeMillis: 1496243474608] [levelValue: 900] [[
alreadyExists failed]]
[2017-05-31T11:11:14.608-0400] [glassfish 4.1] [WARNING] [] [edu.harvard.iq.dataverse.DOIEZIdServiceBean] [tid: _ThreadID=50 _ThreadName=jk-connector(1)] [timeMillis: 1496243474608] [levelValue: 900] [[
String edu.ucsb.nceas.ezid.EZIDException: bad request - no such identifier]]