<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: Encode/Encrypt Fiori/UI5 URL Parameters in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/encode-encrypt-fiori-ui5-url-parameters/qaa-p/13606365#M4818291</link>
    <description>Thanks Edrilan, maybe someone from BASIS end can have some solution.</description>
    <pubDate>Thu, 15 Feb 2024 10:24:19 GMT</pubDate>
    <dc:creator>adnanmaqbool</dc:creator>
    <dc:date>2024-02-15T10:24:19Z</dc:date>
    <item>
      <title>Encode/Encrypt Fiori/UI5 URL Parameters</title>
      <link>https://community.sap.com/t5/technology-q-a/encode-encrypt-fiori-ui5-url-parameters/qaq-p/13604021</link>
      <description>&lt;P&gt;Hi Everyone&lt;/P&gt;&lt;P&gt;We are using both standard and custom Fiori Apps, but URL parameters are visible to users e.g. employee number or document number/year. User is able to change the employee number or any other URL parameters to view details of other documents.&lt;/P&gt;&lt;P&gt;For Example&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fiori App Manage Team is having below URL and user is able to change URL parameter "employee number" to view details of other employees. How to encrypt/encode such URL parameters to restrict access to other records and Odata Query Parameters.&lt;/P&gt;&lt;P&gt;&lt;A href="https://sapessqas.xxx.com:8000/ess?sap-client=999&amp;amp;sap-language=EN#Employee-manageTeam&amp;amp;/EmployeeDetails/00000146" target="_blank"&gt;https://sapessqas.xxx.com:8000/ess?sap-client=999&amp;amp;sap-language=EN#Employee-manageTeam&amp;amp;/EmployeeDetails/00000146&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Note: SSL certificate is already activated may be some profile parameter needs to be maintained from BASIS end to encrypt the URL.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2024 16:09:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/encode-encrypt-fiori-ui5-url-parameters/qaq-p/13604021</guid>
      <dc:creator>adnanmaqbool</dc:creator>
      <dc:date>2024-02-13T16:09:22Z</dc:date>
    </item>
    <item>
      <title>Re: Encode/Encrypt Fiori/UI5 URL Parameters</title>
      <link>https://community.sap.com/t5/technology-q-a/encode-encrypt-fiori-ui5-url-parameters/qaa-p/13605715#M4818217</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;well instead of having a "readable ID" like "00000146" as in your example, you could use UUIDs. But that said that is not really an encryption. And to be honest I would highly question what you try to do here.&amp;nbsp;&lt;/P&gt;&lt;P&gt;URL parameter should not be used to define if someone is authorised to see certain data or not. For that kind of purpose you should use proper authorization roles and authorization checks in the backend. That is business logic and belongs to the backend, not the frontend.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P class=""&gt;Edrilan Berisha&lt;/P&gt;&lt;P class=""&gt;SAP S/4HANA Cloud Financials Development&lt;/P&gt;</description>
      <pubDate>Thu, 15 Feb 2024 00:06:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/encode-encrypt-fiori-ui5-url-parameters/qaa-p/13605715#M4818217</guid>
      <dc:creator>Edrilan_Berisha</dc:creator>
      <dc:date>2024-02-15T00:06:54Z</dc:date>
    </item>
    <item>
      <title>Re: Encode/Encrypt Fiori/UI5 URL Parameters</title>
      <link>https://community.sap.com/t5/technology-q-a/encode-encrypt-fiori-ui5-url-parameters/qaa-p/13606365#M4818291</link>
      <description>Thanks Edrilan, maybe someone from BASIS end can have some solution.</description>
      <pubDate>Thu, 15 Feb 2024 10:24:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/encode-encrypt-fiori-ui5-url-parameters/qaa-p/13606365#M4818291</guid>
      <dc:creator>adnanmaqbool</dc:creator>
      <dc:date>2024-02-15T10:24:19Z</dc:date>
    </item>
    <item>
      <title>Re: Encode/Encrypt Fiori/UI5 URL Parameters</title>
      <link>https://community.sap.com/t5/technology-q-a/encode-encrypt-fiori-ui5-url-parameters/qaa-p/13622295#M4820101</link>
      <description>Hi I am developer myself, so I do not really know what you mean with "BASIS". What you try to do, encrypten the ID to regulate that someone is not easily able to switch is simply not how it should be designed. Nevertheless using UUID is a way as proposed by me.</description>
      <pubDate>Wed, 28 Feb 2024 12:00:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/encode-encrypt-fiori-ui5-url-parameters/qaa-p/13622295#M4820101</guid>
      <dc:creator>Edrilan_Berisha</dc:creator>
      <dc:date>2024-02-28T12:00:17Z</dc:date>
    </item>
  </channel>
</rss>

