How is the Cloud Zoo Server told of Issuer Server URLs?

Hello

I’m probably missing something right in front of my face, or it’s obvious to others except me, or I just need more coffee today but I’m wondering after reading this:

How does the Cloud Zoo Server know the URL of my Issuer Server? I would have thought that, when registering as an issuer, you would need to provide the URL at which the HTTPS callbacks have been implemented but that doesn’t seem to be the case. What am I missing?

Hi Nicolaas,

I don’t know the specific answer to your question, but I know that at some point during the setup you will definitely let the Cloud Zoo know the full URL endpoints of specific endpoints you need to implement. These are configurable by you as an issuer so that you can maintain your system, and there isn’t a “well known URL” standard for these callbacks.

That was one of the things I provided to McNeel (Will) when getting an api credential.

You provide a url such as
myexample.com/myapi/

There are two processes for you to work out with McNeel: the api credential (the place to call and the key) and the signing certificate (to sign plugins with).

Feel free to ask any more questions about setup; I went through the process around November so my memory is still pretty fresh.

Thanks @Nathan_Bossett, it sounds like the template for the email to McNeel doesn’t capture everything you need to send them, because:

It might be obvious to many but just clarifying that you’d need to also supply your API’s address in this email despite it not being mentioned anywhere specifically?

Cheers

Nic

Yes, I had a few pleasant and helpful emails back and forth with Will P in October of last year to finish everything off. I assume he’s still the listed contact in the help files for that part of the process (Brian being the contact for the other part of the process).

1 Like