# Issuer Profile hosted url

**URL:** <https://community.blockcerts.org/t/issuer-profile-hosted-url/939>\
**Category:** Community\
**Created:** [April 3, 2018, 1:22pm UTC](https://community.blockcerts.org/t/issuer-profile-hosted-url/939 "2018-04-03T13:22:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![madison](https://sea2.discourse-cdn.com/flex016/user_avatar/community.blockcerts.org/madison/32/330_2.png) [@madison](https://community.blockcerts.org/u/madison)\
**Post date:** [April 6, 2018, 5:34pm UTC](https://community.blockcerts.org/t/issuer-profile-hosted-url/939/2 "2018-04-06T17:34:38Z")

</div>

I’m guessing you’re talking about the issuer\_id field in the cert-tools conf.ini file.

They talk about how to create that issuer id json file [here](https://community.blockcerts.org/t/verifier-checking-authenticity-fail/245/6).

> generate a JSON issuer identity file with “python create\_v2\_issuer.py -c conf-ini -o issuer.json”. The conf.ini is the same that you are using to generate the certificate template, and to instantiate the certificates. You will find this python module in cert-tools.

I’m not sure you can just plug it in the file like you suggested. It seems like it needs to resolve a url. I’m planning on hosting mine on a site like [myjson.com](http://myjson.com), but you could also just host it yourself if you’re using a webserver, like the one built into flask:

> The previous step will generate a JSON file identifying the issuer, that has to be saved in the exact location that you are declaring in the conf.ini file used also in the previous step. Since I’m using Flask, the line inside the conf.ini looks like:

- issuer\_id = [http://localhost:5000/issuer/issuer.json](http://localhost:5000/issuer/issuer.json)

---

_[View the full topic](https://community.blockcerts.org/t/issuer-profile-hosted-url/939)._