Authentication

These changes are part of the SAP Concur continued commitment to maintaining secure authentication.

SAP Concur support for Hash-Based Message Authentication Code (HMAC) has been deprecated.

SAP Concur provides a Single Sign-On self-service option that enables client admins to set up their SAML v2 connections without involving an SAP Concur support representative.

For more information about the Single Sign-On self-service option, refer to the Shared: Single Sign-On Overview (English Only) and the Shared: Single Sign-On Setup Guide (English Only).

Business Purpose/Client Benefit: This change provides better security and improved support for users logging in to SAP Concur products and services.

Authentication Administration

A new Company Request Token self-service tool is now available to SAP Concur admins who have been assigned the Company Admin or Web Services Admin role.

Business Purpose/Client Benefit: The Company Request Token self-service tool enables clients to generate Company Request Tokens without contacting SAP Concur support. This tool also enables clients to generate a replacement Company Request Token without assistance from SAP Concur support if their Company Request Token expires or is lost.

Client Web Services

On 21 August, the Register Partner Application page was deactivated.

With the October release, a new application management self-service tool will replace the Register Partner Application page.

For more information, refer to the **Planned Changes ** Self-Service Tool for Application Management release note in the September Final Shared Planned Changes release notes (English only).

Prior to the release of the new self-service tool, clients with SAP Concur Client Web Services can contact Client Web Services to register new applications.

Clients who do not have SAP Concur Client Web Services can still contact SAP Concur support to obtain an App ID as needed.

Business Purpose/Client Benefit: The Register Partner Application page was used to create OAuth 1.0 (legacy) applications. OAuth 1.0 was deprecated on 4 February 2017.

For more information about the deprecation of OAuth 1.0 and migration to OAuth 2.0, refer to the SAP Concur Developer Portal.

The new self-service tool for application management will enable clients to create OAuth 2.0 compliant applications.

This feature is no longer targeted for the current release. This Release Note has been moved to the Shared Planned Changes Release Notes (English only).

Concur Mobile App

In late September, the Concur Mobile Registration page will be updated. To navigate to the updated Concur Mobile Registration page, click Profile > Profile Settings > Concur Mobile Registration. The updated Concur Mobile Registration page includes three new sections:

• Mobile Sign-In Policies

• Sign-In IDs

• Download the App

Business Purpose/Client Benefit: The Concur Mobile Registration page update provides users with more information on their sign-in IDs and their organisation's mobile sign-in policies.

File Transfer Updates

This release note is intended for technical staff responsible for file transmissions with SAP Concur products. For SAP Concur customers and suppliers participating in data exchange through various secure file transfer protocols, SAP is making changes that provide greater security for those file transfers.

As of 10 April, 2021, non-SFTP (Secure File Transfer Protocol) protocols and SFTP password authentication are not allowed to connect to SAP Concur for file transfers:

• Non-SFTP file transfer accounts must switch to SFTP with SSH Key Authentication.

• SFTP file transfer accounts that use password authentication must switch to SSH key authentication.

• SFTP password reset requests require the client to provide an SSH key for authentication.

On 12 April 2021, SAP started disabling non-compliant file transfer connections. The process of disabling non-compliant accounts will continue throughout 2021. If you have multiple file transfer connections configured, this change applies to all of your file transfer connections.

This announcement pertains to the following file transfer DNS endpoints:

• st.concursolutions.com

• st-eu.concursolutions.com

• vs.concursolutions.com

• vs.concurcdc.cn

Business Purpose / Client Benefit: These changes provide greater security for file transfers.

This Release Note is intended for the technical staff responsible for file transmissions with SAP Concur. For our customers and suppliers participating in data exchange, SAP Concur is maintaining our file transfer subsystem to provide greater security for those file transfers.

SAP Concur is in the process of migrating entities that currently use a legacy process for moving files to a more efficient and secure file routing process that relies on APIs.

Clients whose entities are currently configured to use the legacy process will be migrated to the more efficient process sometime between now and 24 January 2022. After they are migrated to the more efficient process, clients will see the following improvement:

• With the legacy process, clients had to wait for the file move schedule to run at a specified time. With the more efficient and secure API-based process, extracts and other outbound files from SAP Concur will be available within the existing overnight processing period shortly after the files are created.

This announcement pertains to the following file transfer DNS endpoints:

• st.concursolutions.com

Business Purpose / Client Benefit: These changes provide greater security and efficiency for file transfers.

Files transferred to SAP Concur products must be encrypted with the SAP Concur public PGP key, concursolutionsrotate.asc.

concursolutionsrotate.asc

• Key file is available in client’s root folder

• Key ID 40AC5D35

• RSA 4096-bit signing and encryption subkey

• Key expires every 2 years

• Client is responsible for replacing the key before it expires

  • Next expiry date: 4 September 2022

  • SAP Concur plans to replace the current rotating public PGP key in the client’s root folder 90 days before the expiration date

The SAP Concur legacy PGP key (key ID D4D727C0) remains supported for existing clients but will be deprecated in the future.

SAP Concur strongly recommends that clients use the more secure rotating public PGP key for file transfers. To facilitate the use of the more secure rotating public PGP key for file transfers, SAP Concur added the key to existing client’s home folders on Friday 15 January 2021.

This announcement pertains to the following file transfer DNS endpoints:

• st.concursolutions.com

• mft-us.concursolutions.com

• vs.concursolutions.com

• st-eu.concursolutions.com

• mft-eu.concursolutions.com

Business Purpose / Client Benefit: The rotating public PGP key provides greater security for file transfers.

Localisation

With the September release, SAP Concur plans to change the following terms in the Traditional Chinese version of the SAP Concur user interface to bring consistency to the translation of Attendee(s):

Business Purpose / Client Benefit: These revisions provide a more accurate translation and improved user experience.

Miscellaneous

On 20 September, a new permission, SAP Fiori Theme Preview, will be added to the list of permissions in Concur Travel Professional edition. When the SAP Fiori Theme Preview permission is assigned to a user, the user sees a new switch in the header of their SAP Concur site. They will also see a New Theme info bubble.

The switch enables the user to switch from the SAP Concur standard theme to the SAP Fiori Theme. The info bubble displays a brief message about the switch.

The new theme includes changes to visual elements such as fonts, colours and icons. In addition, some top-level tabs and menu items are relocated to the SAP Concur Home menu. These changes are site-wide and apply to all of the user’s SAP Concur products.

Business Purpose/Client Benefit: The SAP Fiori theme harmonises the look and feel of the SAP Concur UI with the look and feel of other SAP products, providing a more consistent user experience. The permission enables a client admin to allow designated users to preview and test the SAP Fiori theme.

NextGen UI for Concur Request

The continued evolution of the Concur Request solution user interface experience is the result of thoughtful design and research that provides a modern, intuitive and streamlined experience for the request process.

Concur Request customers are now strongly encouraged to preview and then move to the NextGen UI well before the automatic transition date of 1 October, 2022.

Business Purpose/Client Benefit: The result is the next generation of the Concur Request user interface designed to provide a modern, consistent and streamlined user experience. This technology not only provides an enhanced user interface, but also allows us to react more quickly to customer requests to meet changing needs as they happen.

SAP Concur Platform

As of 31 May 2021, the existing Concur Request APIs (v1.0, v3.0 and v3.1) are deprecated. On 1 June 2021, SAP began retiring these APIs in accordance with the SAP Concur API Lifecycle & Deprecation Policy. These APIs are replaced by the Concur Request v4 APIs. SAP will no longer support these APIs after retirement.

Decommissioning of the v1.0, v3.0 and v3.1 APIs will start three months after retiring the APIs. The specific dates for decommissioning are dependent on the individual client's API migration.

API Timeline for v1.0, v3.0, v3.1:

• Deprecation – 1 March, 2020 – 31 May, 2021

• Retirement – 1 June, 2021 – 30 November, 2021

• Decommission – starts after 3 months of inactivity at the retired state

Business Purpose / Client Benefit: The Concur Request APIs v1.0, v3.0 and v3.1 only support the previous authentication method, which is not best security practice and does not meet the Oauth2 standards. In addition, the previous versions of the Concur Request APIs provided limited possibilities for moving a Request through the approval workflow, as well as managing custom simple & connected list fields. These issues are resolved with the new Concur Request v4 APIs.

In addition, SAP has run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 APIs (not ISO-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 APIs.

Test Entities

As per GDPR (General Data Protection Regulation) compliance requirements, clients can submit a Support ticket to request the Right To Be Forgotten (RTBF) for any user in Implementation (Test) entities. A Data Retention Administrator can then follow the steps outlined in the documentation to purge a user from the Test entity.

Business Purpose/Client Benefit: This enhancement is part of the SAP Concur requirement for GDPR compliance.

Web Services Administration

To meet new security requirements, the length of the username and password associated with an application connector must be at least 10 characters long and not more than 50 characters long.

Some clients currently have usernames and passwords configured that do not meet these parameters. In a future release, these parameters will become enforced requirements.

To avoid disruption of callouts through application connections, usernames and passwords that do not meet these requirements must be updated before this change is implemented. SAP recommends updating your application connector username(s) and password(s) as soon as possible.

Application connection usernames and passwords can be updated by an administrator with the Company Administrator or Web Services Administrator role.

Business Purpose / Client Benefit: Enforcing password and username length restrictions improves the security standards for callouts made through the application connector.

Workflow

For the October 2021 release, Concur Request will introduce the ability for SAP Concur administrators to configure event notifications at the workflow step level. When a request reaches a specific step in a workflow that is configured for external notifications, a third-party application will be prompted to complete the required action on the corresponding request.

Business Purpose/Client Benefit: SAP Concur administrators will have more flexibility, as they will be able to create notifications for multiple steps across the workflow for third-party applications.

Customers have use cases and business processes that need to occur in parallel as requests move through the workflow in Concur Request. These event notifications will be an efficient way to start those processes so that requests are approved on time.