<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009fqmo1CAAOkta Identity EngineWorkflowsAnswered2024-10-10T09:01:26.000Z2023-09-19T14:13:56.000Z2023-09-19T16:52:28.000Z
  • TimL.58332 (Workflows)

    @1humy (1humy)​  - RESP looks like a Binary protocol. Workflows is designed to function essentially with Web Server front-ends over the HTTP (text) protocol which commonly have either (REST / SOAP) API behind them.

     

    For Workflows to function in your described scenario there would need to be a means to not only send a command to an endpoint that could then perform the "RESP" function to obtain the results you want. It would also need to be able to return those results to Workflows.

     

    So something like: Workflows > REST > RESP > (the data) > RESP > REST > Workflows.

     

     

    Expand Post
  • 1humy (1humy)

    It would be great if workflows would have that kind of integration, given your answer i will need to implement a proxy http service to redis which causes more network latency and adds an additional layer of support.

This question is closed.
Loading
Redis connector in okta Workflows