22.10.2026 07:59
Service Restored: eADM integrations with Glup and Mer Kompetanse are working again
Problem is fixed, all API endpoints are replying again. We suspect it was downtime due to PHP patching.
22.10.2026 07:59
Service Disruption: eADM integrations with Glup and Mer Kompetanse are down
All our integrations with Moodle-based systems are down, ie: Glup and Mer Kompetanse. We are investigating the cause.
21.10.2026 16:41
Service Disruption: Feide is now available again
Highly critical vulnerabilities were discovered in PHP, which is used in Feide's login service. The vulnerabilities were reported by NSM, CERT-EU, and others, and were deemed so critical that SIKT suspended access to Feide when the details were made public.
SIKT have now installed updated packages that patch the vulnerabilities, and Feide was reopened at 16:40 on 21 October 2026. Please see https://www.feide.no/driftsmeldinger for more information.
Please note that none of Identum’s services use PHP and were therefore not affected.
21.10.2026 16:01
Service Disruption: Feide has been shut down by SIKT
Highly critical vulnerabilities have been discovered in PHP, which is used in Feide's login service.
The vulnerabilities were reported by NSM, CERT-EU and others, and were deemed so critical that SIKT suspended access to Feide when the details were published at 16:00 on 21 October 2026. Please see https://www.feide.no/driftsmeldinger for more information.
Please note that none of Identum’s services uses PHP and are thus not affected directly.
28.09.2026 10:44
Service Disruption: Simployer API back online
The Simployer REST API is back up, and the imports are now running as normal.
28.09.2026 08:37
Service Disruption: Simployer API not responding
We’ve issues with importing data from Simployer, the Simployer REST API does not return data when queried. We’re investigating the issue.
27.08.2026 10:13
Service Disruption: Issues with ID-porten
Update: ID-porten is now stable again and the problem solved according to https://status.digdir.no/incidents/d7tgwqgzd742 .
25.08.2026 07:49
Service Disruption: Issues with ID-porten
-
Systems affected: eADM and eFeide
-
Issue: There are currently operational issues with ID-porten due to a DDOS attack on Digdir’s services.
-
Impact: This affects some users attempting to log in or use the password reset function via ID-porten in the aforementioned systems. Other authentication methods like Feide, Entra ID, Google etc are unaffected.
More information and updates: We are monitoring the situation, but the handling of the situation lies with the Norwegian Digitalisation Agency (Digdir). For continuous updates regarding the status of the resolution, please refer to Digdir's official status page: https://status.digdir.no/
24.08.2026 08:02
Service Disruption: Issues with ID-porten
-
Systems affected: eADM and eFeide
-
Issue: There are currently operational issues with ID-porten.
-
Impact: This affects all users attempting to log in or use the password reset function via ID-porten in the aforementioned systems. Other authentication methods like Feide, Entra ID, Google etc are unaffected.
More information and updates: We are monitoring the situation, but the error originates with the Norwegian Digitalisation Agency (Digdir). For continuous updates regarding the status of the resolution, please refer to Digdir's official status page: https://status.digdir.no/
21.08.2026 10:29
The issue with cost centre codes from Visma Enterprise is now resolved
The issue should now be fixed. If the sync is stuck in the filter, click 'Try again'. This will fetch new data from Visma Enterprise without opening the filter. Since everything is back to normal, the sync should then pass through the filter without stopping.
If the changes slipped through the filter, run a new full sync with the filter disabled to get all the cost centre codes back in place.
21.08.2026 10:29
The issue with cost centre codes from Visma Enterprise is now resolved
The issue should now be fixed. If the sync is stuck in the filter, click 'Try again'. This will fetch new data from Visma Enterprise without opening the filter. Since everything is back to normal, the sync should then pass through the filter without stopping.
If the changes slipped through the filter, run a new full sync with the filter disabled to get all the cost centre codes back in place.
21.08.2026 09:51
Issue with costcentre codes from Visma Enterprise
Overnight, a change occurred in the data provided by Visma Enterprise. What initially appears to be an update to the responsibility codes is actually a clearing of this field, as the codes seem to be either entirely missing or altered for all customers. The exact impact varies from customer to customer.
As a result, a significant number of imports have been halted by the filter, although a few have gone through. For many of you, this will not have any impact, but for those of you with permissions or group memberships linked to responsibility codes:
Please do not approve or let the import through until we notify you that the issue has been resolved.
For those of you who are already experiencing problems, please contact support. We are continuously implementing fixes to get your access restored. In the meantime, Visma Enterprise is working to identify the root cause of the issue.
12.08.2026 09:33
Issue with “Could not communicate with server”
The problem is now solved, and login into eADM is now back to normal.
12.08.2026 08:54
Issue with “Could not communicate with server”
We have an intermittent issue with the warning “Could not communicate with the server” appearing in eADM. We are looking into it.
11.08.2026 08:00
Sync problems with Sikri Elements
This problem is mostly resolved, though a few tenants still have trouble. We are looking into this together with Sikri.
10.08.2026 07:27
Sync problems with Sikri Elements
Sync with Sikri Elements fails with the error message “There was no endpoint listening at https://services05.elementscloud.no/prod/iam2elementsfrosta/service.svc that could accept the message”. We’re investigating the issue.
03.08.2026 16:16
Service Disruption: Issues with ID-porten
Update: ID-porten is now stable again and the problem solved.
03.08.2026 08:06
Service Disruption: Issues with ID-porten
-
Systems affected: eADM and eFeide
-
Issue: There are currently operational issues with ID-porten.
-
Impact: This affects all users attempting to log in or use the password reset function via ID-porten in the aforementioned systems. Other authentication methods like Feide, Entra ID, Google etc are unaffected.
More information and updates: We are monitoring the situation, but the error originates with the Norwegian Digitalisation Agency (Digdir). For continuous updates regarding the status of the resolution, please refer to Digdir's official status page: https://status.digdir.no/