It would be beneficial if the authentication process for the REST data source in the portal could be expanded a bit further.
The addition of an authentication endpoint is a great start, but in our setup, we have a REST API that requires both authentication and a login to execute methods. Moreover, the login also needs to access the authentication token.
Currently, we are executing these methods by storing the login and auth token in a table and then querying them using a Dynamic Values Source Query.
However, it would be more efficient if we could reference these details directly within the query without needing an extra table. This would streamline our authentication workflow and reduce the complexity of managing multiple data sources.
Could we possibly extend this endpoint to include the option to perform both authentication methods and then use them as variables in the methods?
This would greatly enhance our ability to manage authentication within the portal and simplify our current process.
