NFT Manager configuration

To configure the NFT manager, a few things may need to be considered, and some configuration may be required, depending on your situation.

Ways to specify the NFT collection

The default configuration, which will be used if no claim value is present in the authorization request. It can be set in config/idp-config.json. A more detailed overview of all possible claim configurations, can be found in the claim configuration section.

"default_nft_token_claim": {
    "chain": "POLYGON",
    "factorySmartContractAddress": "",
    "smartContractAddress": "0x21dd9b1913d84ab295fdf19834b0b6824a5912ca",
    "collectionPath": ""
}

Possible values for the chain key in both configurations: ETHEREUM, POLYGON, TEZOS, GOERLI, MUMBAI, GHOSTNET.

Activate and specify the OPA policy verification

To activate the OPA policy verification, you may provide some configuration.

"default_nft_policy":{
    "withPolicyVerification": true,
    "policy": "idpkit/opa/nft_tezos.rego",
    "query": "data.app.nft.allow",
    "inputs": {
        "Backgrounds": "Green",
        "symbol": "RMB",
        "reference": "RCS1"
    }
}

Configuration of the wallet connect page

If you don't want to use the default built-in wallet connect page, you can create a nft-config.json file and provide a custom connect page.

{
  "nftWallet": {
    "id": "idpkit-connect-wallet",
    "url": "/connect-wallet",
    "presentPath": "",
    "receivePath" : "",
    "description": "IDP Kit connect wallet"
  }
}