SAP connector fails with No RFC authorization for function module RFC_METADATA_GET error when using Asynchronous Remote Function Call

• The SAP connector was updated to version 5.9.0 and later, deprecating the <sap:async-rfc> action.
• The replacement action, <sap:asynchronous-remote-function-call>, is now used for Asynchronous RFCs
• When using <sap:asynchronous-remote-function-call> call fails with below error - 

Root Exception stack trace: com.sap.conn.rfc.exceptions.RfcGetException: No RFC authorization for function module RFC_METADATA_GET. at com.sap.conn.rfc.engine.RfcImp.ab_rfcerror(RfcImp.java:942) at com.sap.conn.rfc.engine.RfcGet.ab_rfcget(RfcGet.java:195) at com.sap.conn.rfc.engine.RfcRcv.ab_rfcreceive(RfcRcv.java:38) at com.sap.conn.rfc.engine.RfcIoOpenCntl.RfcReceive(RfcIoOpenCntl.java:2103) at com.sap.conn.jco.rt.ClientConnection.executeInternal(ClientConnection.java:2015) at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:2253) at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:2120) at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:2103)

• The updated sRFC feature now includes enhanced validation and accesses the JCo parameter list's metadata. This process necessitates a call to RFC_METADATA_GET. The older, deprecated sRFC bypassed this metadata lookup entirely, instead iterating directly over JCo fields, thereby avoiding any call to RFC_METADATA_GET.