Unable to create Proton resource provider

HCL Domino Domino Forum
,
1

Hi,

I am installing AppDev Pack 1.0.8 on an 11.0.1FP3 Windows server and I am at the point where I need to configure the proton resource provider.

I have defined it in the iam app and I am using the oauthcfg tool to try to import this, however, the oauthcfg tool completes without any output. oauthcfg list shows nothing, and no documents are created in the credstore.nsf.

I am using the command:

oauthcfg create proton-addin <Domino Resource Provider ID> <Domino Resource Provider Secret> https://appdevpackqa.cs4qa.com:7443/token/introspection

I am running it as administrator from the domino directory where the notes.ini is located.

When I execute the command I am seeing nothing on the domino server console either. Is there anything I can do to get more information about this issue?

Regards
Heidi

2

Hi Heidi

Is the notes.ini in the server directory or is this a partitioned server with more than on data directory and therefore more than one notes.ini?

I can reproduce this issue only if I execute the command in a directory that doesn't have notes.ini (which I realize is not the case here).

As a workaround, would you be able to use the Domino server console to execute the create command? For example: load oauthcfg create <name> <id> <secret> <url>. ? The limit for console commands is 255 chars I believe so you should have enough capacity with the given URL. If you're able to use the admin live console, that will make cutting and pasting possible.

3

Hi Gordon,

Thanks for getting back to me. It is a standard Domino server with just one data directory and one notes.ini.

I have Domino installed in c:\Domino with c:\Domino\data as the data folder.

I issued the command in the console and it seems to have worked. It has created the document in the credstore.nsf and from the console I could also do load oauthcfg list and that also worked.

I can now add proton-addin in the adpconfig.nsf also.

Re-running oauthcfg list afterwards on the command line still didn't show anything though.

Happy to provide further info if it helps.

Kind regards
Heidi

4

Hello @Heidi Harding !

You might have incorrect port number in config\local.properties.

Just check/fix it pointing to port 7443 (based on the command that you shared).

I hope it helps!

Please mark this question as answered and helpful if your issue is resolved.

Regards!​

Rodrigo de San Vicente

Staff Software Engineer

Collaborative Workflow Platform