eclipse/kapua

Main lobby for Eclipse Kapua | Kapua 1.4.3 now available! https://github.com/eclipse/kapua/releases/tag/1.4.3

Alex Alexandrov

@MrQuaters

@lorthirk i connecting to another acc, that is child for kapua-sys. The available amount of devices is infinity

RiccardoFelicetti

@RiccardoFelicetti

Hi, I have question. Have you ever tried to use a different MQTT broker for Kapua? Do you know if anyone in the community has ever ask somithing similar?
I mean, we have rabbitmq deployed in the infrastructure and we would like to use Kapua using a unique mqtt broker. I understood looking at the code that Kapua use an ActiveMQ broker with some plugins and listerners etc..

What do you think about that, could be feasible? Of course, the other solution could be to replace our rabbit with ActiveMQ.
Just to know if someone else has haver had this need

thank you

Claudio Mezzasalma

@lorthirk

uhm... never heard of anyone doing that honestly

but yes, I guess that you should port the ActiveMQ plugins to RabbitMQ

RiccardoFelicetti

@RiccardoFelicetti

Hello, I would like to use the sso Keycloak provider available on Kapua, with a personal keycloak instance. But It's not clear for me which parameter I have to set.

For what I read if I want to use a personal Keycloak instance I don't need different deployment script. But I have to set some parameters like sso.openid.provider ....
But I don't undestrand where I have to set those params

Gianluca Barbon

@gbarbon

Hi @RiccardoFelicetti , actually the 'keycloak' provider is intended only to make the configuration easier, but you can configure a keycloak instance also using the 'generic' provider.

As for the deployment scripts (I imagine you refer to the docker ones), the sso-docker ones are intended to be used as a demo Keycloak instance, which is automatically started with the same scripts. As you said, if you already have an existing instance you can use the normal scripts.

The only thing that is missing on the normal script are the sso 'env' variables in docker-compose.yml file. However, they will be soon added with PR 3260 ( see here eclipse/kapua#3260 ).

Gianluca Barbon

@gbarbon

As for the 'env' variables to be set, you can find a description (for the 'generic' provider) here: https://github.com/eclipse/kapua/blob/develop/assembly/README.md#generic-provider

(there is also some documentation on the developer documents, here https://github.com/eclipse/kapua/blob/develop/docs/developer-guide/en/sso.md; here the parameters are detailed only from the 'property' point of view, which can also be used to configure the sso, but IMHO using bash 'env' variables it's easier)

Gianluca Barbon

@gbarbon

@RiccardoFelicetti if you want to contribute with some detailed documentation about Keycloak 'env' variables, feel free to open a dedicated PR, that would be nice! :)

RiccardoFelicetti

@RiccardoFelicetti

Thank you for the answer. I read the https://github.com/eclipse/kapua/blob/develop/docs/developer-guide/en/sso.md properties explanation here. Now i'm trying to set up this variables from the docker-compose.yml. Doing something like this:

"JVM_OPTS=

  -Dsso.openid.provider=keycloak 
  -Dsso.openid.keycloak.realm=myrealm 
  -Dsso.openid.keycloak.uri=http://myKeycloakinstance:80 
  -Dsso.openid.client.id=my-client-id
  -Dconsole.sso.openid.home.uri=http://localhost:8080"

is it correct

I add these configuration parameter in the kapua-console service, in the environment field

RiccardoFelicetti

@RiccardoFelicetti

At the end I was able to do that using the following env var on the docker-compose: KEYCLOAK_URL, KAPUA_CONSOLE_URL, KEYCLOAK_REALM, KEYCLOAK_CLIENT_ID.

Gianluca Barbon

@gbarbon

At the end I was able to do that using the following env var on the docker-compose: KEYCLOAK_URL, KAPUA_CONSOLE_URL, KEYCLOAK_REALM, KEYCLOAK_CLIENT_ID.

That's correct, those are the 'env' variables that I was referring to.

RiccardoFelicetti

@RiccardoFelicetti

About this keycloak integration, I'm able to perform the login with the console. How does it work with the API? How can I login with a "keycloak account" from API ?

Gianluca Barbon

@gbarbon

you should see an 'SSO login' button in the login dialog box

that will redirect to a Keycloak page in order to login with a Keycloak user credential

RiccardoFelicetti

@RiccardoFelicetti

Yes, this is what I do using the console

But If I want to use the API(Swagger)?

Gianluca Barbon

@gbarbon

Ok, now I got it. For the moment the single sign on login flow through REST API is not yet implemented

RiccardoFelicetti

@RiccardoFelicetti

ok, thank you !

Claudio Mezzasalma

@lorthirk

well, I guess you can obtain an idToken from your SSO and use it as a credential in /authentication/jwt

RiccardoFelicetti

@RiccardoFelicetti

Hello, ok I'm gonna try this thank you

Today I receive this error when I try to manage Kura asset from Kapua

Caused by: org.eclipse.kapua.transport.exception.TransportClientGetException: Cannot get an instance of the transport client to connect to host: tcp://broker:1893

I don't understand where the 1893 port is taken

I didn't change the environment variables

Kapua Api service gives me that error

RiccardoFelicetti

@RiccardoFelicetti

Also, I'm trying to override the env variable "BROKER_ADDR" with another hostname but the error is still the same

teamrdwitti

@teamrdwitti

Hi all, I have a registered device that publishes measurements (we can view them in the tab "Data"). But when we want to have a look to its settings, the tab "configuration" is empty and a blue error popup appears on the right hand side with the message "Selected device not connected. Please refresh device list". Any help would be greatly appreciated ;)

Claudio Mezzasalma

@lorthirk

@RiccardoFelicetti there has been a change on how other internal components communicate with the broker

I think it's in eclipse/kapua#3066

Hi all, I have a registered device that publishes measurements (we can view them in the tab "Data"). But when we want to have a look to its settings, the tab "configuration" is empty and a blue error popup appears on the right hand side with the message "Selected device not connected. Please refresh device list". Any help would be greatly appreciated ;)

@teamrdwitti which version?

Pedro

@pintify

Package download endpoint has this warning:

However, how could I know the operationId I should look for?

In case it must be searched in /operations endpoint "manually", which id should I use, for the operation object has two different ids:


        {
            "type": "deviceManagementOperation",
            "id": "LwLogSRx13I",
...
            "operationId": "SfWNEoZY1FQ",
        },

Claudio Mezzasalma

@lorthirk

nice question. I THINK you should be using operationId

Pedro

@pintify

Great, thanks! And is there a way to achieve the operationId I need without inspecting all the operations?

Claudio Mezzasalma

@lorthirk

uhm... probably @Coduz is the best person to ask :D

Laurent Carré

@sterwen

Hello, got a very strange phenomenon when trying to connect a gateway with Kura to Kapua

06:23:03.210 [ActiveMQ NIO Worker 4] INFO o.e.k.b.c.p.KapuaSecurityBrokerFilter - User name newborn-gw - client id: BS184300124, connection id: ID:bdc7ff7e684a-45167-1599078074822-5:47027
06:23:03.221 [ActiveMQ NIO Worker 4] WARN o.a.a.broker.TransportConnection - Failed to add Connection id=ID:bdc7ff7e684a-45167-1599078074822-5:47027, clientId=BS184300124 due to {}

The gateway indicates it is connected, I see a connection in Kapua but nothing in devices

Where communities thrive

People

Repo info

Activity