3384145 - Potential scenarios affected by HTTPS enforcement in SAP Ariba Solutions

To ensure that SAP Ariba can securely transmit data, receive data, and display URLs in the user interface and email messages, SAP Ariba will enforce the use of HTTPS URLs starting with the 2310 service pack. Customers will need to update URLs from HTTP to HTTPS, and reconfigure their outbound endpoint URLs to HTTPS as soon as possible.

• What potential consequences might there be at the application level?

  • Web service/Managed Gateway for Spend & Network outbound integration,

    • Log in to Ariba Procurement Application (Buyer site) and Navigate to:
    • Manage > Core Administration > Integration Manager > Integration Configuration
    • Log in to Ariba Strategic Procurement Application (Sourcing site) and Navigate to:
    • Manage > Administration > Integration Manager > Integration Configuration
    • For the enabled webservice/Managed Gateway for Spend & Network (Outbound), verify the URLs defined. If the customer are using http, the integration will be impacted.

• • Updating only the web service/Managed Gateway for Spend & Network outbound URL from http to https will resolve the issue?

• • • Updating the outbound url to https is enough from Ariba side. However, the customer has to coordinate/verify with their Admin/Infrastructure team and confirm that they accept https request URL. If they are not accepting the request, then the outbound call with be impacted.

• • URLs links in RSS feeds

    • Log in to Ariba Procurement Application (Buyer site) and Navigate to:

    • Manage > Core Administration > Manage Administration > Dashboard Managers > Dashboard Templates > Configure > Edit

    • Log in to Ariba Strategic Procurement Application (Sourcing site) and Navigate to:

    • Manage > Administration > Manage Administration > Dashboard Managers > Dashboard Templates > Configure > Edit

• • URLs defined on parameter/configuration files

    • Kindly review the parameter via Intelligence Configuration Manager (ICM).

    • Article explaining the parameter change via ICM How do I manage site parameters with Intelligent Configuration Manager (ICM)?

    • ICM Parameter list Intelligent Configuration Manager Parameters Reference

    • If the parameters are controlled by Ariba, then you have to create a support ticket with Ariba Platform team.

• • URLs in email notification

    • The custom url added to the email notification with reference to HTTP at the content level.

• • Guided Buying (GB) action tile links

    • In GB, URLs are defined at the landing page/Target URL. Kindly download the landing page and review the tile configuration.

• • Terms and condition with Http Url

    • Terms and condition can get added based on the Print preview Template on Purchase orders, invoices or other documents. The corresponding template/files needs to be located in order to update the URLs.

• • Clickable links in Flex Fields

  • URLs defined in custom field/web jumper

  • Catalog files (CIF, XML, and other formats) have some affected fields (Supplier URL, Manufacturer URL, Images, AuxiliaryImages, AuxiliaryThumbnails, and other fields).

    • Log in to Ariba Procurement Application (Buyer site) and navigate to:
    • Manage > Core Administration > Catalog Manager > Search for catalog subscription > Select the Active version > Click Export Tool
    • Then search for http: in the catalog file.
    • If the catalog file is integrated from Business Network to Ariba Buyer, request the supplier to update the details and push the file.

• • Supplier punch out catalogs

• • • Log in to Ariba Procurement Application (Buyer site) and navigate to:
    • Manage > Core Administration > Catalog Manager > Search for catalog subscription > Select the Active version > Click Export Tool
    • Then search for http: in in the catalog file.
    • If the catalog file is coming from Business Network to Ariba Buyer, then kindly request the supplier to update the details and push the file.

• • Inbound web service integration (should already enforce use of HTTPS).

  • For Integration ToolKit (ITK) via file Channel, the value for parameter "urlPrefix" or argument customer is using for defining the URL for import/export events needs to point to HTTPS.

  • Field reference at the template level (Sourcing, Contract & SLP)

• • Endpoints defined at Business Network for P2P, Sourcing , GB and integrations
    • Kindly refer to : https://support.ariba.com/item/view/KB0397804?

Http to https changes , KBA , BNS-ARI-PCP-BF , Base Framework , BNS-ARI-SS , Strategic Sourcing , BNS-ARI-INV , Invoicing , BNS-ARI-PUR , Purchasing , BNS-ARI-CM , Catalog Management , BNS-ARI-SB , Spot Buy , BNS-ARI-CP-CORE , Core Administration , How To