Jay Sundu (Feb 22 2024 at 22:53): Jay Sundu (Feb 22 2024 at 22:53):Hi there.
I hope everyone is well.
I'm attempting to set up our instance with EZID as the DOI provider and am not able to mint DOIs.
I am using the following jvm options:
<jvm-options>-Ddataverse.pid.ezid.username=ucblibrary</jvm-options>
<jvm-options>-Ddataverse.pid.ezid.password=${ALIAS=doi_password_alias}</jvm-options>
<jvm-options>-Ddataverse.pid.ezid.api-url=https://ezid.cdlib.org</jvm-options>
Is this what Dataverse expects?
Also how can I turn on additional logging for this?
Thanks much! Jay
Philip Durbin 🚀 (Feb 23 2024 at 00:51):Hmm, is DataCite an option for you? The reason I ask is that I'm not sure if the EZID provider is still working or not. It's California-only so its use is limited these days.
Philip Durbin 🚀 (Feb 23 2024 at 00:51):@jamie jamison you don't happen to use EZID, do you?
jamie jamison (Feb 23 2024 at 00:54):I do use EZID , - a UC decision. I'm at 5.14 and my code reflects that
Philip Durbin 🚀 (Feb 23 2024 at 00:55):Oh! So it does still work. Phew!
jamie jamison (Feb 23 2024 at 00:55):Working just fine. Looks like the 5.14 documentation.
Philip Durbin 🚀 (Feb 23 2024 at 00:56):Does anything jump out at you about the config above? I think it looks ok to me. :thinking:
jamie jamison (Feb 23 2024 at 00:57):It certainly seems to match. At this point I might start picking through logs and probably go to you for help.
Philip Durbin 🚀 (Feb 23 2024 at 00:58):@Jay Sundu what about the database settings listed at https://guides.dataverse.org/en/6.1/installation/config.html#configuring-your-dataverse-installation-for-dois ?
Philip Durbin 🚀 (Feb 23 2024 at 00:58)::Authority for example
Sherry Lake (Feb 23 2024 at 14:37):@Jay Sundu
You will need these set (which it seems that you do):
JVM Options for EZID:
dataverse.pid.ezid.api-url
dataverse.pid.ezid.username
dataverse.pid.ezid.password
https://guides.dataverse.org/en/latest/installation/config.html#configuring-your-dataverse-installation-for-dois
AND you need these set:
:DoiProvider
:Protocol
:Authority
:Shoulder
UVa has....
":Protocol": "doi",
":DoiProvider": "DataCite", - you will need ":DoiProvider": "EZID",
":Authority": "10.18130",
":Shoulder": "V3/",
Our Autrhority is 10.18130
Our Shoulder is "V3/" (with the slash) Our DOIs look like: https://doi.org/10.18130/V3/ZGS4T4
We had EZID in the beginning (before it was limited to UC schools) and the "V3" was given to us by EZID as a shoulder.
Jay Sundu (Feb 23 2024 at 14:52):Thank you @Sherry Lake and @Philip Durbin . I did see a error in the database settings and have retested. I'm waiting on confirmation. I'm hopeful it will now work and I much appreciate the responses! Stay tuned, I will report back here.
Jay Sundu (Feb 23 2024 at 17:40):Success! Thanks @jamie jamison @Philip Durbin @Sherry Lake !!!
Jay Sundu (Feb 23 2024 at 21:20):Jay Sundu said:
Success! Thanks jamie jamison Philip Durbin Sherry Lake !!!
I spoke too soon. Its working in staging but I'm seeing this in prod. Note nceas.ucsb.edu referenced. I've double-checked that staging config matches prod. Any thoughts on where this misconfig might be? Why does it think I'm nceas?
[2024-02-23T12:48:30.192-0800] [Payara 6.2023.9] [WARNING] [] [edu.harvard.iq.dataverse.DOIEZIdServiceBean] [tid: _ThreadID=97 _ThreadName=http-thread-pool::jk-connector(3)] [timeMillis: 1708721310192] [levelValue: 900] [[
String edu.ucsb.nceas.ezid.EZIDException: unauthorized]]
I wouldn't worry about nceas in edu.ucsb.nceas.ezid.EZIDException. That's just showing who wrote the Java library we use.
Philip Durbin 🚀 (Feb 23 2024 at 21:23):Unauthorized, huh? Do you have a different username and password for prod? That's how DataCite does it.
Jay Sundu (Feb 23 2024 at 21:30):It should be the same username/password -- I'm using the same api-url. When setting the password with asadmin, I accidently did create-password-alias doi_password_alias (instead of update-password-alias) I then updated it and just now deleted and created it again thinking this looks like it's not accepting the password for some reason.
Philip Durbin 🚀 (Feb 23 2024 at 21:36):Woof. Password alias stuff. Not my strong suit.
Philip Durbin 🚀 (Feb 23 2024 at 21:37):You could temporarily put the password in plain text just to confirm it's working.
Jay Sundu (Feb 23 2024 at 21:37):How can I try that - I'd give it a shot.
Philip Durbin 🚀 (Feb 23 2024 at 21:38):Well, in domain.xml the username is in plain text, right?
Jay Sundu (Feb 23 2024 at 21:38):Oh. I guess hardcode it into the domain yeah.
Philip Durbin 🚀 (Feb 23 2024 at 21:38):just as a test
Jay Sundu (Feb 23 2024 at 21:45):Okay that worked. So something is messed up with the alias.
Philip Durbin 🚀 (Feb 23 2024 at 21:49):It's tricky. I never use it in dev. Maybe next week we can ask Don Sizemore for help.
Philip Durbin 🚀 (Feb 23 2024 at 21:49):It's quittin' time here on the east coast. :grinning:
Jay Sundu (Feb 23 2024 at 21:50):Oh gosh yes. Enjoy the weekend and thanks again. I'm off for three weeks so you'll be hearing from me then.
Philip Durbin 🚀 (Feb 23 2024 at 21:50):Three weeks. Nice. Enjoy!
Jay Sundu (Feb 23 2024 at 21:50):Baby bonding time with my six-month old son!
Philip Durbin 🚀 (Feb 23 2024 at 21:51):Aw. Mine are teenagers now. You can see one in #community > good vibes . Enjoy that baby time!
jamie jamison (Feb 23 2024 at 21:52):Thank you Phil for all the help for those of us getting started!
Philip Durbin 🚀 (Feb 23 2024 at 21:52):It's my pleasure. I didn't write this code for people to not be able to use it! :crazy:
Last updated: Oct 30 2025 at 06:21 UTC