In desperation, help requested

[raymondandreassen]

Hi, I'm trying to build a command line client for Harica as a replacement for Sectigo. I have a specific task that the client library needs to support. In short, I'm having trouble with authentication, and I see you've solved it. Can I ask for your help?

I get the header field:

• RequestVerificationToken, from __RequestVerificationToken.
• Authorization from a rest api call, which returns a valid web token as text, with quotation marks.

The jwt token signature "failes" on jwt.io. I just assume it's not signed, and I process it as a regular webtoken.
So far, so good. But I must say, a bit of an unconventional method Harica has chosen.

Next step is to build the rest api call with http header and the three attributes. Harica's instructions:
In the Cookie header type in the phrase HARICA= and then the same value as RequestVerificationToken.
This is where I think my problems are, the cookie addition to the headers. The instructions are straight forward, but I cannot make sence to it. When browsing and inspecting a regular webpage, the value is something else than the value from _RequestVerificationToken. It begins similar, but it's much longer.

Whatever I do, all rest api calls I send with the three headers set, a html login page is returned.
Let it be said; I have no idea where I go wrong. My main suspicion is the cookie header.
Do you have some tips for me? I feel I have tried almost everything.

[fritterhoff]

Hi,

yeah. The docs of HARICA are sadly not that good and the API is a little bit picky.

I've stumbled over the same issue(s).

In detail you must preserve the Cookie Header and don't change it at all. In our tool this is done by using an internal cookie store.

[raymondandreassen]

It was a fight, took me almost a full day, but now I have found that little bugger.
Now I can code up the utility I need.
Thank you for your info, it probably saved me many hours of frustration.

[fritterhoff]

Just in case it is not to specific I would consider to integrate it here?