22 posts tagged with "connect"

An incremental update to improve the experience for long running requests.

To update already deployed applications to no longer have timeouts:

1. Create a new package
2. Deploy the new package to your existing application

• [Bugfix]: Removed HTTP timeout from deployed applications allowing SAP to handle timeouts

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.

Patch to address customer submitted issues.

Notes:

1. To make use of the new Accept-Language feature in an existing app, a new package needs to be created with the same selected APIs and published to the existing app. Please find notes on packaging and publishing APIs in our packaging docs

Known Issues in this release:

1. Publishing a package may result in a System.NullReferenceException in CheckConnectivityServicesStep.cs or CheckAuthorizationStep.cs.
   1. To resolve this issue, navigate to your App Details page, click the Re-auth SCP button and follow the steps in the wizard. After the wizard completes, your package should publish successfully.

• [Feature]: Translation Language for returned descriptions can be requested using the Accept-Language header.
• [Update]: Search context RIO's without a leading structure are now supported.
• [Update]: Added additional configurable output logging for diagnosing response messages from SAP
• [Update]: Performance improvements in data serialization
• [Bugfix]: Service hub url parameter for manual deployments to docker are correctly using secure wss transport, fixing cannot connect issue.
• [Bugfix]: Port was being stripped off of the connection string in SAP connections, causing issues when connecting to SAP systems using a custom proxy server.
• [Bugfix]: Fixed a race condition in the console viewing documentation without a project.
• [Bugfix]: Fixed a docker access issue consuming a base image for new applications

Fix to address orphaned sessions in SAP

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

• [Bugfix]: Connecting to any SAP client ID (by service account or SAP Cloud Connector) now works as expected

This bugfix release resolves issues with handling structures in RFC's and corrects parsing of different SAP date types.

• [Update]: Added support for structure parameter types in RFC API's
• [Bugfix]: Fixed parsing of different date component types returned in RIO's and RFC's

• [Bugfix]: API end points no longer shut off 30 days post-deployment

This release consists of primarily bugfixes, but also introduces a new session handling approach.

Known Bugs:

• Deleting an app does not always remove it from SAP Cloud. Workaround: Remove manually from inside the SAP Cloud Cockpit.
• Occasionally, after an app deployment or package publishing, the app status does not go back to active properly. Workaround: refresh the browser.
• If you are running in 'Passthrough' authentication mode, in Swagger portal, when you use the "Authenticate" button at the top of the page, there are two logins presented. You should use the top one. Workaround (to avoid remembering which one you want): using the lock icon on any of the API calls will present a single box that will work (for all APIs on that connection).

• [Feature]: New session handling approach using distinct API calls vs. the session parameter on individual API calls
• [Update]: Changed email provider for password resets
• [Bugfix]: Dialog box when publishing a package no longer says "done" prematurely
• [Bugfix]: Authentication now properly turns off when changed in the app authentication tab
• [Bugfix]: Package docker naming convention updated to simplify manual deployment
• [Bugfix]: Improved handling of SAP connection errors
• [Bugfix]: Parameters in EnosixDocument search RIO now work properly
• [Bugfix]: Docker images now last more than 30 days

This is a small patch to fix an issue preventing the activation of pass-through authentication on an app.