Closed innonav-dev closed 12 months ago
We think we recall that there was an issue in v19 with bclicense - sorry - too long ago. I'd say, in these older, unsupported, versions - stick to the flf.
ALOps merely imports a license - not much we can change about inner workings of downloading symbols or anything like that.
Did switching to flf solve the problem And - does it work with bclicense for the newest versions?
going back to flf solved the problem. Newest versions are working properly Thanks
Describe the bug Upon switching from flf License Files to BCLicense Files in BC Version 19.2, a
403 Forbidden
error is triggered during the ALOPS - Compile Extension Task.The used yaml
The output The error message displayed is as follows:
Log content from ALOPS License Import and ALOPS Compile Extension have been recorded as shown below.
ALOPS License Import Log Content:
ALOPS Compile Extension Log Content:
Expected behavior The expected behavior would be for the ALOPS - Compile Extension Task to execute without returning a 403 Forbidden error, and for the extension to compile successfully.
Additional context The bug surfaced after a change in license file type was made, from flf to BCLicense, in BC Version 19.2.