c-open | CANopen stack for embedded devices | Automation library

Found the solution

WHY this issue was coming: Docker build (to create the image) was run on a machine (the other machine, where cmake was working inside the docker container)... i.e. where FIPS was not installed. During the build step, Docker file was running zypper install cmake (or yum install cmake).

As FIPS was disabled on the machine where docker image was built, cmake was installed in docker image, without understanding FIPS being enabled / dracut-fips being installed.

Then, when you copy this image and consume it on a machine where FIPS is actually ENABLED, then cmake was failing with that error mesg: crypto/fips/fips.c:153: OpenSSL internal error: FATAL FIPS SELFTEST FAILURE

--

Solution #1: Tag your docker image appropriately.

Summary:

PS: If you do install cmake using the above, then it'll only work on target machine where you run container, if that machine's FIPS is disabled or enabled at build time. i.e. if FIPS was enabled, you install cmake and run it on a machine where it's NOT same FIPS setting as the host, where image was built, then you'll be reading this post for help.

Better way in case you want to install cmake using the above package managers, would be, tag your docker image appropriately during image creation time i.e.:

docker build -t -fips-enabled ... if FIPS is enabled

and

docker build -t -fips-disabled ... if FIPS on that that machine is disabled.

That way, you can pick the correct docker image imagename-fips-enabled vs imagename-fips-disabled acc. to what your target machine FIPS setting is (where you'll actually perform docker run ... using this image).

--

Solution #2: Don't use zypper (OpenSuse) or yum if you have RedHat container. and this solution is flexible in the sense, that it's independent of FIPS setting = 0 / 1 on the host, where image was built.

I didn't use zypper/yum to install cmake inside Dockerfile, but just grabbed cmake-3.18.2-Linux-x86_64.tar.gz bundle file.

Within Dockerfile, I simply extracted this .tar.gz file inside some directory. Also I set export PATH:/path/where/I/installed/cmake-3.18.2../bin:/..some_other_paths:/...:/.... in Dockerfile inside RUN statement.

i.e. RUN export PATH=/path/where/I/installed/cmake-3.18.2../bin:/...... && && && ... etc, so it can find the extracted cmake 3.18.2 for any buil-time (cmake operations) and also SET the same PATH=/... variable as ENV PATH=/.... same value used during RUN for PATH so at runtime, when the container runs, $PATH is all set for finding cmake (3.18.2 version) rather than using any existing /usr/bin/cmake or some other shit).

Dockerfile snapshot:

Adding x-* to the security model is not possible with config (at the moment). But I think that would be a valid feature to request, so please do so in the issues.

What you can do for now is to create your own Filter (that is all that it is under the covers).

See https://download.eclipse.org/microprofile/microprofile-open-api-1.0/microprofile-openapi-spec.html#_oasfilter

And the current filter in Quarkus: https://github.com/quarkusio/quarkus/blob/main/extensions/smallrye-openapi/deployment/src/main/java/io/quarkus/smallrye/openapi/deployment/filter/SecurityConfigFilter.java

I hope you need to try this URL.

http://localhost:8080/swagger-ui/index.html?configUrl=/v3/api-docs/swagger-config#

My Configurations

Also, I have created a OpenAPI bean

Your problem is that you're finding all the occurences of "title" in the page. Beautiful soup has an attribute title specifically for what you're trying to do. Here's your modified code:

The correct way is not to expect swagger from implemented interfaces, but build it from api.yml file. This config in application.yml helped me:

The imports and usage of the library is correct. The version also includes the method that you want, I've just checked.

This indicates that the compiler is unable to locate the relevant jar on the classpath.

Can you please run mvn install and if it reports any errors add them to the original post and also add a comment here to notify me.

EDIT:

The “cannot find symbol” error comes up mainly when we try to use a variable that is not defined or declared in our program.

When our code compiles, the compiler needs to verify all identifiers we have. The error “cannot find symbol” means we're referring to something that the compiler doesn't know about.

As it turns out, in your case it is a dependency version conflict which can be detected and resolved like this https://pretagteam.com/question/conflicting-library-version-in-a-java-maven-project

StaleElementReferenceException: stale element reference: element is not attached to the page document

Indicates that a reference to an element is now "stale" --- the element no longer appears on the DOM of the page. The reason for this expectation is may be your DOM got updated or refreshed. For an example, after performing an action like click() your DOM may get updated or refreshed. In this time when you are trying to find an element on DOM you will experience this error.

You have to re-find that element in updated or refreshed DOM

All right, I found a way to make it work, albeit with the implicit flow and a dedicated second (public) client in Keycloak.

The Quarkus application.properties:

Spring Boot 2.5.x requires Spring HATEOAS 1.3. As you have seen, downgrading to 0.x will not work.

The 1.0 release of Spring HATEOAS included a number of breaking API changes. You should use EntityModel in place of Resource and WebMvcLinkBuilder in place of ControllerLinkBuilder. You can learn a little more in this blog post. There's also a script that can be used to help with the migration.