20 posts tagged with "link"

🔊 We now support Destination Services and Single Sign-On (SSO) 🔊

1️⃣ You can now configure your Link BTP app to use Destination Services with Principal Propagation with SSO and/or Location ID.

Destination Services that are supported:

• Principal Propagation for SSO
• Passthrough (No Auth)
• Basic Authentication

For more information, See our documentation: https://docs.enosix.io/link/destination-configuration

2️⃣ You can now configure your Link App to authenticate using XSUAA service for Principal Propagation (SSO) through Service Instances.

For more information, See our documentation: https://docs.enosix.io/link/principal-propagation

FEATURES:

1️⃣ Support was added to utilize the Destination Service and inject Location ID.

2️⃣ Support was added for authentication/authorization using XSUAA.

📣 We have added new low-code features for administering your Link instances in 3.1. 📣

1️⃣ When a cookie with a static value is desired on all requests to SAP, this can now be injected in Link through configuration. Cookies and their values can be configured per route so the client does not need to attach the cookie manually. For more details, see the documentation.

2️⃣ A new start-time metric will be visible from the /health endpoint the Link instance. This information can be used to manually derive other metrics for your Link instances' health.

• [Feature]: Cookie values can be injected into requests to SAP through configuration
• [Feature]: Start-Time metric is exposed on the /health endpoint

New landing page for deployed link instance

See updating to the latest release for details on how to use the landing page. The new landing page can be disabled, and is outlined in the Link product documentation.

The new metrics health check has been added to monitor any potential issues in processing requests.

{
  "Metrics": {
    "status": "Healthy",
    "description": "",
    "data": {
      "requests-per-second": "0",
      "total-requests": "3502",
      "current-requests": "0",
      "failed-requests": "0"
    }
  }
}

• [Feature]: A new landing page providing information on the version and links to documentation
• [Feature]: Basic request metrics for monitoring performance of a Link deployment

Updates to support SAP SSO O-Auth. This latest version has been tested to work with our Salesforce SAP Auth Provider for named credentials allowing for password-less per-user access to SAP.

• [Bugfix]: Proxy of url encode form content added

Announced on Dec 10th, 2021 the Zero Day Log4j vulnerability CVE-2021-44228, is affecting systems worldwide. enosix has reviewed its systems and has yet to detect any platforms, apps, or services that are affected by this vulnerability.

Salesforce is conducting its own analysis of its systems. Any Salesforce apps provided by enosix (Surface, Transact, Commerce, CPQ) are not using log4j and are not affected. Salesforce will provide updates to the Salesforce platform, if needed.

The enosix connect platform does not utilize java or the log4j libraries and is not affected. Your IT department should review any other apps you are running in the SAP BTP platform, see SAP Note 3130476

enosix Link does not utilize java or the log4j libraries and is not affected. SAP Note 3130868 details that none of the SAP Cloud Connector versions contain the affected log4j-core and are not affected.

enosix will continue to review our systems and provide assistance. We advise that all computer systems operators review their systems that may be affected and take the recommend steps to patch any affected software.

Updated link version with improved documentation

https://docs.link.enosix.io/

• [Feature]: Use Checkly to monitor outages, add end to end monitoring and alerting to your link instances following our guide.
• [Update]: Updated runtime to dotnet core 3.1, this fixes many CVE's and memory issues

The documentation for enosix Link has a new home: https://docs.enosix.io (or https://docs.enosix.io/link to go directly to the Link documentation).

This release addresses security issues for the 2.2 release

• [Update]: PSA: Your SAP cloud connector certificate will expire every year. Please ensure to update the certificate prior to expiration by following the instructions here EXTERNAL LINK: SAP Cloud Connectivity issues due to Expired Certificate

Link now supports multiple connections per app instance. A single deployed application in SAP Cloud Foundry can now define multiple routes to different virtual hosts. This reduces the number of deployed applications needed for development and test environments, and Cloud Foundry memory allocation requirements.

Link latest and stable have been updated to this release 2.2.22

Please see the link documentation for install instructions.

• [Feature]: Link version is now returned in health check endpoint /health, and included as a response header enosix-link-v. This will assist in ensuring the most up to date version of Link is deployed, Additionally the enosix-link-v header is captured in your Salesforce Surface logs viewable in the Salesforce enosix app for debugging.
• [Update]: Version naming change, previous versions were prefixed with the year and the release number, ex: 2020.1.12, going forward link versions will follow a Major.Minor.Patch version scheme. with this release 2.2 the successor of 2020.1.12. The existing labels for enosix/link:stable will be updated with this release.
• [Bugfix]: Fixed issue with configuring multiple connections within a single instance. Note: this was mainly used in development and QA connections.

This release fixes the intermittent connection error that would happen every 30-40 min and then would resolve after about two minutes.

• Fixed logic for authentication refresh token to SAP Cloud Connector proxy.

Ensure your manifest file is using the stable image, see below. Restart your link application instances in the Sap Cloud Platform Cockpit to perform the update.

docker:    
  image: enosix/link:stable

enosix Link Docs

• [Bugfix]: Fixed proxy authentication to SAP Cloud Connector. (Intermittent connection error every 30m)