This new release includes defect fixes and addition of minor functions for the 2.5 release, and is recommended for all 2.5 installations.
New/improved features
Now possible for the administrator of the system to publish customer-defined information or news in the UI. This helps the administrator to spread important information such as planned downtime, new features or hints.
To forward information to the IdP, there is an option to set cookies at login, can be used for example to remember login option or source of user
Defect fixes
The 2.5.4 release includes important defect fixes for the 2.5 release, including
Retention time settings for an errand lifecycle, possible to disable PDF validation and GUI fixes
See full patch release information for 2.5.4 here:
PhenixID is proud to announce the new release of PhenixID Authentication Services (PAS) 5.1.0. The new release improves the stability, compatibility, and security of your solution, and is recommended for all installations.
HIGHLIGHTS
The 5.1.0 version introduces a new way of configurating Authenticators, exceptionally simplifying for administrators by giving more control of authentication flows. In addition to this, increased built in support for SAML and OIDC protocols and updated guides for configuration makes this 5.1.0 release something that will not just make PAS more secure but also reduce complexity.
Authenticators architecture
Clear separation of protocols versus authentication methods, new simplified configuration guides to support easier and faster configuration. Read more about how this will make the administrators life easier here.
OpenID Connect support
significantly more OIDC functionality now available “out-of-the-box” in code instead of via manual configuration. Also some new OIDC support not previously possible, e.g Hybrid Flow support. Link to documentation here.
SIGN transaction for BankID and Freja EID
Force a SIGN request to BankID or Freja eID with clear information to the user on the intention of signing
PhenixID are proud to announce the new release of PhenixID Identity Manager 6.1.2. The new release improves the stability, compatibility and security of your solution, and is recommended for all installations.
Maintence release
PIM 6.1.2. mainteance release resolves the following issues
PIM-1381 MULTILISTSTRINGCONTROL HANGS
PIM-1382 DEFAULT VALUE HIDDEN IS SENT TO AS EMPTY VALUE TO PIP
PIM-1388 CUSTOM CONTROL FAIL TO RETURN DISPLAY NAME WITH SPECIAL CHARACTERS
PIM-1393 NO SCROLLBAR IN MAIN MENU IF YOU COLLAPSE THE WIDTH
PIM-1395 MULTILISTSTRING IS NOT DISPLAYED INTERMITTENTLY
PIM-1401 MANAGER SEARCH ENGINE STOPS WORKING WHEN INCORRECT NAME/LETTERS IS TYPED AND SEARCHED
PIM-1411 FORMS PATH IS SET TO OTHER FORM
Read the full release notes for Identity Manager 6.1.2 here
PhenixID Signing Workflow 2.5.0 improves the stability, compatibility and security of your solution, and is recommended for all installations.
HIGHLIGHTS
The highlight for the 2.5.0 release includes the ability edit already created errand
Edit errand
Prior to this release, the only thing that was possible to update on an errand was the expiration time. If the wrong person was invited as a signer, or someone was missing, a soliciotor had to delete the old errand and create a new one. Signers who had already signed the document had to sign again. This release adds the possibility for the solicitor (via GUI or API) to edit an already existing errand
Signers that hasnt yet signed can be removed
New signers can be added
The descirption of the errand can be updated
The priority order for signers who hasnt yet been invited (in queue) can be changed
Reminding signers
In the configuration its possible that a emial reminder is sent prior to the errand expires. Now a solicitor can also trigger a reminder email to a signer that hasnt yet signed by clicking a button in the GUI
IMPROVED FUNCTIONS
SWF graphical issues (mobile responsiveness) has been resolved
BUG FIXES
IGA-467 Do not log out when changing language’ IGA-504 Runtime error when uploading first document
Read the full release notes for Signing Workflow 2.5.0 here
PhenixID is proud to announce the new release of PhenixID Authentication Services (PAS) 5.0. The new release improves the stability, compatibility, and security of your solution, and is recommended for all installations.
HIGHLIGHTS
Finally the PAS 5.0 version see the light of day! This version is a major technical upgrade, compared to 4.7 and earlier versions. It brings significantly better security level as well as futureproofing and enabling of further enhancements. There are no significant changes in terms of functionality or usability in this initial 5.0 version.
Increased security
PAS 5.0 includes a significant reduction of software security vulnerabilities in third party librariues used. The build and testing of PAS software has been enhanced by a mandatory vulnerability (OWASP) check, meaning that the software build process will catch known vulnerabilities – in each recurring and scheduled build.
Upcoming features
As PAS 4.7 branch is moved to maintenance mode, new and enhanced features will be developed and released on this new 5.0 branch. This strategic move ensures that new features are built on a more modern platform.
Inclusion of additional modules and valves in the product
Prior the 5.0 release, some specific modules and valves were treated as standalone entities necessitating separate installation procedures. By consolidating these components into the core product, you benefit from a more cohesive and streamlined life cycle management process, guaranteeing the availability of the latest and most secure versions – thereby fortifying the overall integrity and security of the system
Known limitations
Initially we recommend this version for those using internal HSQLDB database or MSSQL only
Read the full release notes for Authentication Services here:
PhenixID Signing Workflow 2.4.0 improves the stability, compatibility and security of your solution, and is recommended for all installations.
HIGHLIGHTS
The highlights for the 2.4 release includes the ability invite external signers using email address as well as the possibility for the solicitor to validate current signatures wihtou downloading the document
Invite signers using email
Prior to this release, it was possible to invite signers from the organizations AD or to add them based on personal number. In some scenarios this could not be enough
Asking for, or storing, personal numbers can be sensitive. Organizations could for example have policies saying its not allowed
Sometimes the exact signer isnt known, for example in the case where someone at a subcontractor firm should sign
The 2.4 version allows the solicitor to invite a signer using only email address. Important to know is that anyone with access to the mail could open the mail and sign it, so it is important that the solicitor at completion verifies that the signee is expected.
Validation of signatures
PhenixID Authentication Service has a function to validate the authenticity and integrity of a signed document. Added in 2.4 release is the possibility to trigger such a validity check directly from SWF GUI.
IMPROVED FUNCTIONS
SWF SW shown for solicitors and administrators
BUG FIXES
IGA-470 Emails not sent when errand has expired
IGA-499 Tag values not reset after order created
IGA-500 Failed to decode downloaded font error
Read the full release notes for Signing Workflow 2.4.0 here
This new release includes defect fixes and addition of minor functtions for the 4.7 release, and is recommended for all 4.7 installations.
Bug fixes
The 4.7.2 release includes important bug fixes for the 4.7 release, including
App switching on iOS17 for BankID, Freja eID and SITHs, making sure the user doesnt manually have to switch back to the correect browser. Security vulnerabilities mitigated. Problems with internal federations at restart. SAML updates including support to handle large requests, handling missing scope and AuthnContectClassRef
New/updated features
More attributes available from Freja eID including documentType, documentSerialNumber and photo. Possiblity to force PipeAuthenticator to always be triggered
See full patch release information for 4.7.2 here:
This new release includes defect fixes and addition of minor functtions for the 4.7 release, and is recommended for all 4.7 installations.
Bug fixes
The 4.7.1 release includes the following fixes
PHX-2963 resp_attributes type 6 (Service-Type) value returned incorrectly
Service-Type attribute in RADIUS always returned the wrong value.
Now updated and the Service-Type attribute can now be set using PropertyAddValve
PHX-3030 Wrong language is show in PSS if brower is set to Swedish
If Chromium based browser have Swedish as default language, the Password Selfservice service would show a mix of English and Swedish
PHX-3068 Signing, OCSP/CRL: Incorrect validation
Validation of OSCP/CRL tokens failes since wrong value is compared
PHX-3110 BankID – 400 response when signing gives Java error
BankIDSignValve and BankIDCollectValve woudl generate a java error if BankID returns a 400 response.
The solution also includes an update where the errorcode of the 400 response is forwarded to the application
PHX-3122 IOS redirect to native browser when using non native browser
Independent of which browser is used when initiating a BankID authentication, iOS devices will redirected back to default web browser
PHX-3170 Add loginhint to OIDC to auth-request
Support for “login_hint” in OIDC auth-request is missing
PHX-3188 Clear “SAMLSignApproved” with the rest of the SAML attributes on a new SAMLRequest
Attribute SAMLSignApproved is not cleared
PHX-3189 validateSchema for SAML SignMessage causes freeze/crash in some environments
validateSchema function in SAMLAuthRequestDecoder freezes/chrashes, preventing SignMessage to be parsed
New/updated features
PHX-3021 Add support for basic authorization in bankid proxy module
Support basic authorization header in BankID proxy/api
PHX-3102 SithsEidCollectAuthenticationStatusValve that returns Inera response intact as json
Return the intact Inera response as json
PHX-3108 BankID 6.0 Phoneauth via proxy/api
Phoneauth endpoint according to BankID 6.0 added in BankID proxy/api
PHX-3112 OpenID Connect Session Management 1.0
Support for OpenID Connect Session management 1.0 implemented
PHX-3126 Add BankIDPhoneSignValve
Add BankIDPhoneSignValve according to BankID 6.0
PHX-3127 Make it possible to expand requirement from request in BankIDAuthenticateValve and BankIDSignValve
Add the possibility to add requirements in a request when using HTTP API with BankID valves
PHX-3171 BankID 6.0 Phonesign via proxy/api
Add Phonesign endpoint according to BankID 6.0 to BankID proxy/api
PHX-3187 Make AssertionConsumer strict scoped attribute validation option
Let the administrator decide by config if AssertionConsumer should use strict scoped valdiation or not
See patch release information for 4.7.1 and read the full release notes for PhenixID Authentication Services 4.7 here:
PhenixID is proud to announce the new release of PhenixID Identity Provisioning (PIP) 6.3.3. The new releases improves the stability, compatibility, and security of your solution, and is recommended for all installations.
MAINTENANCE RELEASE
IMPROVED FUNCTIONALITY
PIP-721 Add a body option to the REST DELETE Handler action
REST DELETE Handler now have the possibility to include a body to the delete requests
PIP-723 Add a Copy post action
Select a post in the LDAP tree that you want to create an copy of and point to the OU where the copy should be saved
PIP-731 Improve SQL action to handle errors
Any errors in a SQL write action is now also included as an attribute in the return value of the action
BUG FIXES
PIP-720 Syntax Attribute Validation is not emptied after a successful syntax is read
PIP-722 Retrieving large multivalues will eventually take the enumerating LDAP connection, causing corruption and closed LDAP connection
PIP-724 WriteToLDAP: Not always setting error attribute on failure
PIP-725 Policy Debugger: Large text attributes are slow to render
PIP-726 Settings multiple schedules from policy tab does not get saved
PIP-727 Import objects dialog: No error handling for missing icons
PIP-729 Import Prefix writes to Schedule reassign
PIP-732 Write to LDAP action sometimes does not write Binary to ldap
PIP-735 Session transmitter does not work
Read the full release notes for Identity Provisioning 6.3.3 here
PhenixID Signing Services Workflow 2.3.0 improves the stability, compatibility and security of your solution, and is recommended for all installations.
HIGHLIGHTS
The highlights for the 2.3 release includes the ability to delete signing errands and the possibility to anonymize the information about a specific user (GDPR compliance)
Deleting errands
All errands are saved in the SWF database for future reference, althought the actula document can be deleted after a configured lifetime. Organizations might have policiys to delete information about digital errands after a specific time. It could also be that errands that arent successul (maybe someone refused to sign) chould be removed right away to avide clutter. Added in 2.3 there are 3 different ways to delete an errand
Scheduled jobs – configure the lifetime of errands for a specific state
Delete signing errand via GUI
Delete siging errand via API
Anonymizing signer
Siging errands in SWF database include information about the people set to sign, information that could include AD usernaname, e-mail address or social security number (“personnummer”). General Data Protection Regulation (GDPR) adopted by European Union in 2016 regulates the use and ownership of personal data. It includes the right for any person to be forgotten and have their information removed from any data storage.
To help the administrator to comply with GDRP, SWF 2.3.0 includes the possibility to anomynize a user. The administrator can execue a job to anonymize a user based on either UUID, personnummer, username or email address. At anonymization, errans including the user that has asked to be forgotten are updated and all information about this user are replaced with “anonymized”, however still present in the errand database. For example, a errand including users john.doe and jane.doe, where john.doe is anonymized will still be present but when opened it says that the signers are “jone.doe” and “anonymized”.
IMPROVED FUNCTIONS
In addition, several features have received minor improvement including:
Added additional Java arguments for Hazelcast in the startup scripts to get the best performance results
Set notifyUser parameter via API
Minor GUI improvements
BUG FIXES
IGA-434 Can’t change language
IGA-438 Empty defaultLanguage config value cause crash
Read the full release notes for Signing Workflow 2.3.0 here
PhenixID is proud to announce the new release of PhenixID Authentication Services (PAS) 4.7. The new release improves the stability, compatibility, and security of your solution, and is recommended for all installations.
HIGHLIGHTS
The highlights for the 4.7 release include support for BankID RP-API v6.0, support for new Skolfedartion and multiple SAML updates.
BankID Säker Start RP-API v6.0
PAS 4.7 now have support for BankID RP-API v6.0 released mid May. This release is part of BankID “Säker Start” to improve security for BankID users by removing support of starting a BankID transaction where the user fills in their Personnummer. Services should instead use QR Code or Autostart, both already supported by PAS in earlier versions. It is strongly recommended to update to RP-API v6.0, by updating to PAS 4.7, since BankID will end support for earlier versions already May 1st 2024
PAS 4.7 supports both new v6.0 and previous version, making it possible for the administrator to migrate to v6.0 in a controlled and secure manner. PhenixID will help with guides on best-practice for migration. Don’t hesitate to contact PhenixID for more information about BankID Säker Start and what is needed on the service
Skolfederation
In March, Skolfederation together with Internetstiftelsen released a new version of Technical Profile for SAML WebSSO for Skolfederation. PAS 4.7 release complies with this new profile and are ready to be used for all entities connected to Skolfederation
SAML and EFOS
Several updates for the SAML protocol has been added to fully comply with the EFOS specification. These updates are generic and will be beneficial for all SAML installations
Improved functions
In addition, several features have received minor improvement including:
MyApps have been updated to comply with WCAG
Improved error handling using authenticators
Improved debug logging for HTTP valves
Miscellaneous bug fixes
Defect fixes recommended for all users, including
PHX-2899 Internal SAML: Entity not found
PHX-3029 Dispatch based on query string in OIDCToSAMLBroker
PHX-3047 FrejaEID login on same device does not take you back to the original app after auth
PHX-3083 EFOS – SAMLResponse must be signed
PHX-3084 EFOS – Include information on what failed to validate
PHX-3086 EFOS – Error in SAMLAuthSigning documentation
PHX-3087 EFOS – SAMLAuthForSigning error when not logged in
PHX-3088 EFOS – PrincipalSelection value missing in SAMLAuthForSigning
PHX-3089 EFOS – signMessageDigest addtribute always added – not documented
PHX-3090 EFOS – Encrypted signMessage doesnt work
PHX-3091 EFOS – PAS crash when Assertion is encryted and signed
PHX-3092 EFOS – Config example for solution missing
PHX-3094 EFOS – Requestedauthncontext missing if no dispatcher
PHX-3095 EFOS – Multiple AuthnContextClassRef
PHX-3096 EFOS – AssertionConsumerServiceURL fail for LOA4/HOK
This new release includes defect fixes for the 4.6 release, and is recommended for all 4.6 installations.
Bug fixes
The 4.6.2 release includes the following fixes
PHX-3037 Add PKCE support to the OIDC RP Relay authenticator
Now supports PKCE when acting as Relying Party in OIDC. See documentation of Open ID Connect Relying Party under Authenticators for how to enable in your setup
PHX-3049 WCAG MyApps
MyApps GUI now updated to align with WCAG 2.1
PHX-3100 XML Parser security improvments
Updated handling of XML parsing
PHX-3104 OIDCToSAMLBroker when session already available
OIDCToSAMLBroker returns login data when an authenticated OIDC session already exists and prompt is set to “none”
See patch release information for 4.6.2 and read the full release notes for Authentication Services 4.6 here:
PhenixID is proud to announce the new release of PhenixID Authentication Services (PAS) 4.6. The new release improves the stability, compatibility, and security of your solution, and is recommended for all installations.
HIGHLIGHTS
The highlights for the 4.6 release include updated HTTP API for BankID, Freja eID and SITHS, addition of Freja eID in “verify user” template and valves for BankID SIGN with QR code support.
BankID QR code support via HTTP API
Updated BankID logotype accorinding to BankIDs new release
Freja eID QR code support via HTTP API
Freja eID can now be used in the Verify User template
Use SITHS-eID as API authenticator
Possibility to disable appswitching in BankID authenticator scenarios
Improved functions
In addition, several features have received minor improvement including:
Key rollover for SAML Service Provider Authenticators
Secured sensitive endpoints as default
Added support for dynamically setting Assertion Consumer Service URL in the AuthNRequest for SAML Service Provider Authenticators
Disabled support for TLS versions prior TLS 1.2
Miscellaneous bug fixes
Defect fixes recommended for all users, including
PHX-2995 – Fixed PDF preview rendering issues while zooming and changing page
PHX-3003 – Resolved HSQLDB backup issues using default backup location
PhenixID Signing Services Workflow 2.2.0 improves the stability, compatibility and security of your solution, and is recommended for all installations.
HIGHLIGHTS
The highlights for the 2.2 release includes the addition of Admin user role and the possibility to use Tags on errands
Admin user
In previous versions of SWF, there was two different roles for users:
Signers who is allowed to sign documents in errands assigned to them
Solicitors – apart from the same permissions as the signer – is allowed to create and manage siging errands
But what do you do if a specific Solicitor gets unavailable (for example gone on vacation or sick leave) and you need to handle a specific errand belonging to that Solicitor? The SWF 2.2 release includes a new role, admin, which can perform everything a Solicitor can do but also manage all errands created by any Solicitor. Simply put, a specific Solicitor can only see errands he/she has created while a admin user can see both errands created him/herself but also errands created by other Solicitors.
Tags
Some information might be available at creation of an errand, but isnt really applicable until the errand has finished. As an example, at create you might know that this document that is signed is a employment contract or you have information that this document should be archived in a specific archive. When the errand has been signed by all signers decisions should be made depending on that earlier information. Using the earlier examples, the employment contract should be sent to HR and the archive intended might mean that the document should be saved on a specific location.
This release introduces the use of Tags. Tags is a way to save information through the lifetime of the errand. At creationg Tags can be set and the settins of these tags can then be read until the errand is deleted. This could be specificaly benefitial when using the API to create and query errands. At completetion the script that implements the use of SWF API can querry about the tag settings and use that information to take decisions
IMPROVED FUNCTIONS
In addition, several features have received minor improvement including:
Possibility to control the format of a Swedish personnummer. If forcing the format ot 12 digits the administrator of the system can always be sure that the return value from for example BankID or Freja eID can always be matched with the solicitors input
Generic GUI improvments for increased usability
BUG FIXES
IGA-402 Setting expire date manually sets expire date one day before actual setting
IGA-412 Admin list filter and nav not visible when filtering
Read the full release notes for Signing Workflow 2.2 here
PhenixID is proud to announce the new release of PhenixID Identity Provisioning (PIP) 6.3.2. The new releases improves the stability, compatibility, and security of your solution, and is recommended for all installations.
MAINTENANCE RELEASE
BUG FIXES
PIP-710 Three view showing incorrect states
PIP-711 Actions interface does not synch changed objects
PIP-712 Common Connection Pool unstable
PIP-713 LDAP Query: Binary attributes not working
PIP-714 Policy Runner: DEBUG logging stops snooping
PIP-715 Run Policy: Mapping parameters wrong
Read the full release notes for Identity Provisioning 6.3.2 here
PhenixID is proud to announce the new release of PhenixID OneTouch for iOS and Android. The new release improves the stability, compatibility, and security of your solution, and is recommended for all users.
HIGHLIGHTS
The latest OneTouch release includes:
Dark mode support
Adaption to iOS and Android graphical user interface framework
Profile cards updates
Miscellaneous user interface updates
This latest version (5.1.1 for iOS and 5.2.3 for Android) are available in the on the following platforms:
PhenixID is proud to announce the new release of PhenixID Authentication Services (PAS) 4.5. The new release improves the stability, compatibility, and security of your solution, and is recommended for all installations.
HIGHLIGHTS
The highlights for the 4.5 release include compliance to DIGG “Deployment profile for the Swedish eID framework”, animated QR code for BankID and WCAG 2.1 updates.
Supporting DIGG’s “Deployment profile for the Swedish eID framework”
PDF/XML signing cert key size < 4096b
Animated QR code for BankID
FrejaID authenticator scenario added (QR code, same device, other device)
SQLImportTool for migrate from HSQLto MySQL/MSSQL
Improved functions:
In addition, several features have received minor improvement including:
Possible to configure userVisibleData for BankID identification just as with signing.
Configuration of GenerateJWTTokenValve target property name available.
WCAG 2.1 updates to Password Selfservice and MyApps.
Miscellaneous bug fixes
Read the full release notes for Authentication Services here:
PhenixID is proud to announce the new release of PhenixID Identity Provisioning (PIP) 6.2.2. The new releases improves the stability, compatibility, and security of your solution, and is recommended for all installations.
HIGHLIGHTS
IMPROVED GENERIC WORKFLOW
Addition and updates of features to improve the workflow for the administrator working with the tool daily. This helps that administrator to complete tasks simpler and faster. Updates include
Now possible to sort multivalues in session attributes
Actions are always sorted by categories (user are free to decide the category of a specific action)
Import objects dialog can now be set to (default selected) to hide objects that are identical to objects already existing in the configuration
New action that will remove duplicate multivalues in selected attributes
POLICIES
Enforcement of explicit policies sorting now available – possible to prioritize policies used frequently.
The actions tab on a policy will now allow selection of and operating on multiple actions simultaneously.
DATA SOURCES
When working with a file data source (CSV), its now possible to decide if whitespaces should be remover or kept.
For the LDAP data source, it is now possible to configure a number of maximal attempts to try connecting before failing hard.
LIBRARIES
Identity Provisioning is now tested and bundled with java 17.0.4_1 from Azul, and the release contains several other fixes that are recommended for all customers.
The SOAP library has been updated from Axis1 to Axis2, mainly for hosting of SOAP web services
Miscellaneous bug fixes
Bugfixes and updates of current featureset
Read the full release notes for Identity Provisioning 6.2.2 here, Identity Provisioning 6.2.1 here, and Identity Provisioning 6.2.0 here
PhenixID are proud to announce the new release of PhenixID Identity Manager 6.1.1. The new release improves the stability, compatibility and security of your solution, and is recommended for all installations.
HIGHLIGHTS
LANGUAGE IMPROVEMENT
With PIM 6.1.0 we introduce overlay using language. This means that there will for English and Swedish be two language files for each language used. (PIM still support the addition of several languages, for any other custom language file there will be only one file.)
OTHER MISCELLANEOUS IMPROVEMENTS:
Session Time-Out Improvements
LDAP Connectivity Improvement
CSS Updates
UI Improvements
Version 6.1.1 includes further fixes on errors introduced with 6.1.0.
Read the full release notes for Identity Manager 6.1.0 hereand for Identity Manager 6.1.1 here
PhenixID is proud to announce the new release of PhenixID Identity Provisioning (PIP) 6.1.4. The new releases improves the stability, compatibility, and security of your solution, and is recommended for all installations.
HIGHLIGHTS
LOG SETTINGS CHANGES AFFECTED IMMEDIATELY
In previous versions you needed to close and start the PIP Configurator or restart the service for when changes of log settings was made.
For this version:
– PIP service. PIP service will read the log4j2.xml every 30 seconds. So no need to restart service any more.
– PIP Configurator. When changes to log settings are made, general settings or policy based settings, the PIP Configurator will refresh new setting when you click save. So no need to close and start the PIP Configurator any more.
POLICY LOGGING NOW SUPPORTS FOLDERS
When configuring logging for specific policies, it is now possible to specify both the folder and the filename for the log file.
REST ACTIONS: TLS CLIENT AUTHENTICATION
For the REST Actions (GET, POST, PUT, DELETE, PATCH), new parameters have been added for allowing TLS Client Authentication (Mutual TLS) when connecting to the server.
Miscellaneous bug fixes
Identity Provisioning is now tested and bundled with java 17.0.3_7 from Azul, and the release contains several other fixes that are recommended for all customers.
Read the full release notes for Identity Provisioning 6.1.4 here
PhenixID are proud to announce the new major release of PhenixID Authentication Services 4.0. The new release contains several new features both for administrators and end users.
Highlights:
User experience
We have extended versatility to our PhenixID One Touch client (that is included in the offering) to do anonymous assignments/or QR-code login to diversify end-user friendly log in methods. This enables a higher security posture since no username or password is exposed! See video below:
Furthermore the PhenixID One Touch client now supports “on same device app- switching” for a smooth user journey.
Reporting, Audit, Visibility
In our continuous efforts to add system intelligence and awareness we have implemented a heartbeat responder in order to assure the system is responding.
A popular logging feature that we now have added is trace_ID to make it easier to follow an authentication from start to end from a log perspective.
SITHS eID (Swedish only)
En video som visar inloggning via PhenixID Authentication Services med Inera´s nya SITHS eID som inloggningsmetod.
Metoder som används i filmen:
Dator – SITHS-kort
Dator – Mobilt SITHS eID
Telefon – Mobilt SITHS eID
PhenixID MFA adapter integration med Microsoft ADFS för Inera´s nya SITHS eID metoder för autentisering. Inloggningen i denna film sker genom att använda metoden QR-kod.
QR-kod på dator
QR-kod på mobil.
Extended database handling
As the industry keeps pushing for a smooth and resource efficient environment we have from this release decided to further unlock tailor options. With this release it is now possible to separate different parts of the authentication flow and utilize different data source setups. The new improved design will help administrators to tailor their database setup.
