This is just to bring more clarity on Alex's post, in case not to late: CSRF Protection – Connectivity – SAP Library
Cross-site request forgery – Wikipedia, the free encyclopedia Looking forward to your feedback, let me know if some of my assumptions are not correct.
Unfortunately (again), there is no way how to set http header parameter for fileuploader, so you need to redefine it by yourself and change the logic as it is described in this post Re: FileUploader and X-CSRF-Token?. Same logic applies here as the previous issue. Unfortunately, there is no link between fileuploader and ODataModel, so fileuploader needs to handle token validation by itself. In this case, you need to first fetch CSRF token, adding header parameter X-CSRF-Token : Fetch, read its content from response parameter x-csrf-token and add it manually to header of your testing modify request.Ĥth issue – You are sending files to SAP Gateway using sap.ui.commons.FileUploader and you are getting 403 HTTP response – CSRF token validation failed If you do not provide the token, you will receive 403 HTTP Forbidden response with following message “CSRF token validation failed”. 3rd issue – You are using external REST client for testing modify operation You should fetch CSRF token before every modify operation, if you want to prevent your user to see HTTP 403 response.
There are several blog posts in SCN using this library. 2nd issue – You are using datajs library and OData.request for your modify operations So the outcome of this finding is that you do not need to use method refreshSecurityToken() unless you turn off bTokenHandling or you want to implement some special fuctionallity when refresh fails. I did not find information when openui5 started to support this functionality, but you can check it in debugger that after creating ODataModel instance, bTokenHandling is set to true by default. ODataModel has a parameter called bTokenHandling that takes care about token handling. 1st issue – You are using ODataModel for modify operations and not calling refreshSecurityToken() method before them There are different ways how the token is handled. When you do not provide fresh security token with modify request, the user can end up with 403 error message and his recent entry in some form will be most likely lost. By default, the security session management is active in these releases.” Release >= 7.03/7.31, the validity is bound to the security session, which depends on the system parameter http/security_session_timeout value (see transaction RZ11 for details on this parameter). Release _) and this CSRF token remains valid for 24 hours (86400 seconds).Ģ. “ The validity of the CSRF token depends on the release of the ABAP component SAP_BASIS and on the activation of the security session management (which is controlled via the transaction SICF_SESSIONS on the granularity of SAP clients):ġ. In my case, I found out that the validity of token is set to 30 minutes. The validity depends on your settings and SAP_BASIS release. If the provided token is not correct, gateway responds with HTTP 403 (“Forbidden”) return code. Prevention from this attack is based on keeping security token during user’s session and providing it with every modify operation (PUT, POST, DELETE). What is CSRF, why do we use CSRF token and how long it is validĬSRF (Cross-site request forgery) is type of attack, when attacker tries to send malicious requests from a website that user visits to another site where the victim is authenticated. Since I found some misleading content here in community network, I would like to share with my findings. Lately, I was struggling with correct handling of this token.