ALM_OCTANE_TECH_PREVIEW header issue

[machinedata]

Can anyone confirm that they're able to use the ALM_OCTANE_TECH_PREVIEW header value with the API. I believe I'm passing this correctly in the headers, but the response is 403 error code.  I'm on the latest version (12.60.47.104) of Octane.

The simplified log below shows the authentication request, followed by another to the preview API.  I'm successful authenticating to Octane, and non-preview API requests work just fine.

[Debug] Connected to Octane: OK
[Debug] ====================================
[Debug] Starting Signin
Authorization: Basic XXXXXXXXXXXXX
Accept: application/json
ALM_OCTANE_TECH_PREVIEW: true

[Debug] Response
[Debug] ====================================
[Debug] OCTANE_USER Value is XXXXXXXXXXXXX
[Debug] LWSSO_COOKIE_KEY Value is XXXXXXXXXXXXX

[Debug] Starting Request
[Debug] ====================================
Host: 192.168.2.158:8080
ALM_OCTANE_TECH_PREVIEW: true
Set-Cookie: OCTANE_USER=XXXXXXXXXXXXX, LWSSO_COOKIE_KEY=XXXXXXXXXXXXX
Accept: application/json

Any suggestions would be greatly appreciated.

[Dirk Hedderich]

Hi,

Which tech preview items do you want to access and with which functionality? Then I can try this in my code.

I am using ALM_OCTANE_TECH_PREVIEW = true for some items in the GDPR Content Pack - but I also use the legacy HPECLIENTTYPE="HPE_REST_API_TECH_PREVIEW" since older Octane versions need it.

And openly I was lazy figuring out where I still need the headers or where I could remove them since new Octane versions do not need them any more...

Regards,

Dirk

[machinedata]

Thanks Dirk,  I was trying to access the audit resource and getting the 403 error. 

Otherwise my requests are being handled correctly.  I was comparing my code to the published .NET SDK but didn't see any real difference there, but will keep looking.

[Dirk Hedderich]

The online help states the auditing entities are technology preview (https://admhelp.microfocus.com/octane/en/latest/Online/Content/API/Audit.htm). I assume you've used example code from that page to verify your statements? Which exact statement did you try?

But it's strange: When I check against "my" Octane on SaaS environment (12.60.52.74) it shows that the "audit" entity is private...

I assume you use Octane on premise: Could you try setting the legacy configuration parameter "ENABLE_LEGACY_TECH_PREVIEW_CLIENT_TYPE" to true and add the header "HPECLIENTTYPE" = "HPE_REST_API_TECH_PREVIEW"?

Cheers,

Dirk

[machinedata]

Thanks Dirk, 

Yes I am using Octane on-premise.  The query I'm attempting is very basic:

http://<server>:<port>/api/shared_spaces/<id>/workspaces/<id>/audits

Even tried other variations for workspace, shared_space and site.

I've also tried ENABLE_LEGACY_TECH_PREVIEW_CLIENT_TYPE set to true, with the HPECLIENTTYPE header variable as well. Same result as before.

Interestingly, querying the list of entities doesn't list an audit entity in the result, but I'm not sure whether that's because of the ALM_OCTANE_TECH_PREVIEW setting or not.

-MD

[Sigal_Ishay]

Hi, can you specify which Octane on-prem version are you using? thanks, Sigal

[Dirk Hedderich]

Hi Sigal,
He mentioned " I'm on the latest version (12.60.47.104) of Octane."
Cheers,
Dirk

[machinedata]

Octane 12.60 CP10

[Sigal_Ishay · Accepted solution]

Thank you for your feedback,

Indeed the audit API is not available yet and planned to be available on November release, even though it was documented.

We will make sure to update the documentation as eventually the feature was not released but the documentation was not updated.

On November release we plan to introduce both Audit API and Activity Log UI which will enable workspace admins in a very simple way to search for past activities and view the entire history of the workspace also via the UI.

stay tuned 🙂