[
https://issues.apache.org/jira/browse/FLINK-29363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607848#comment-17607848
]
Gabor Somogyi commented on FLINK-29363:
---------------------------------------
I've had a deeper look at this issue and here are my findings.
{quote}So the setup would be that there's an authenticating proxy between the
Flink Web UI and Flink's REST API.
The problem is currently that if a REST API call fails, the UI will just break,
instead of redirecting to another page.
{quote}
Yes, this is the main issue. Adding redirect could be used for authentication
renewal and/or routing to specific IP address based on user account.
{quote}I guess based on the HTTP error codes?
{quote}
Yes, basically 401 comes back in case of authentication failure but adding that
would be not super generic.
I think it would be better to handle redirection which is not bound to auth
failure.
{quote}One problem I see is that this setting is purely used in the UI, so we
need a way of forwarding a "global setting" to the UI ... but I guess that's
solvable.
{quote}
Adding unconditional redirect handling wouldn't require any config. Of course
we can introduce something if you think needed.
> Allow web ui to fully redirect to other page
> --------------------------------------------
>
> Key: FLINK-29363
> URL: https://issues.apache.org/jira/browse/FLINK-29363
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Web Frontend
> Affects Versions: 1.15.2
> Reporter: Zhenqiu Huang
> Priority: Minor
> Labels: pull-request-available
>
> In a streaming platform system, web ui usually integrates with internal
> authentication and authorization system. Given the validation failed, the
> request needs to be redirected to a landing page. It does't work for AJAX
> request. It will be great to have the web ui configurable to allow auto full
> redirect.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
