Fiware IDM server issue
I am using Fiware IDM version 6.2 and i have issues with keystone server (running on port 5000)..
Keystone is working fine until server is not used for some amount of time (around 1 hour) after that first call that arrive ( in my case from pep-proxy checking auth token) it simply enter into unresponsive mode, meaning it does not send anything back. When i cancel request and send it again it start working normal.
I would like to know if there is something on my part that i missed or failed to check.
I am using docker to run Fiware IDm enviroment.
Picture of logs
You are using an old version both Keyrock and Wilma. Currently, both of them are in version 7.5.1. Please take a look on Hub Docker (https://hub.docker.com/u/fiware). Nevertheless, the issue that you mention is due to security management. The admin tokens expire after 1h, therefore you need to obtain a new one to continue working with it.
- Orion context broker doesn't create tenant databases "on the fly"
- Connect system which includes OPC UA IoT Agent, Orion Context Broker. Cygnus and Historic data with Postgres
- ERROR: Pool overlaps with other one on this address space
- Displaying Irrelevant Sensor Data in FIWARE Orion When Using IoT Agent-JSON and Mosquitto
- Get all Fiware-ServicePath for a specific Fiware-Service
- FIWARE PEP Proxy Wilma server fails to start
- FIWARE Orion-LD upsert replace endpoint: only attributes or completely (including type)?
- FIWARE FIROS Publish cmd_vel from Non-ROS-World
- IoTAgent (JSON) over MQTT doesn't receive measurements from mosquitto
- Orion sending error message "connection failed, after 100 retries"
- Orion-ld fails to establish a connection with the MongoDB Community Operator due to a connection string issue
- How to get the missing table Schema while using quantumleap in cratedb using orion LD context broker though the subscriptions are working?
- yum error "Cannot retrieve metalink for repository: epel. Please verify its path and try again" updating ContextBroker
- Specifying attributes to be aggregated by STHSink
- Why Orion-ld after 0.8.0 is not supporting the formation of service/subservice in quantumleap logs?
- issues configuring a device via bidirectional attributes using IOT agent JSON and Orion LD
- Error downloading and installing Java JDK in CentOS (FIWARE)
- Context provider application: MongoDB connection unsuccessful
- How to maintain a FIWARE apikey?
- How to get the servicePath from /v2/entities GET call
- Orion APIs authentication through Keycloak
- My dockerized service doesn't receive the notification sent by Orion Context Broker
- How to send massive data of sensors in Orion
- Notify python orion/quantumleap subscription changes
- Can I send a notification in the creation and deletion of an entity?
- HTTP POST request gets transformed to GET request
- Orion APIs authorization through Keycloak
- Fiware orion /op/query endpoint working explaination
- Subscription between Orion context broker and Quantumleap works, but table is not created in CrateDB
- Calling external APIs through fiware orion context broker to validate using keyrock