From b0a50a7e80e9b6a2d8aaa44c74b350a4aab51dc7 Mon Sep 17 00:00:00 2001 From: David Woodhouse Date: Thu, 9 Aug 2018 11:27:08 +0100 Subject: [PATCH] Don't treat Juniper 'realm' field as authgroup The only point in the authgroup thing for the UI is to allow OpenConnect to re-request the set of query fields for the new group. But the Juniper protocol doesn't do that, and it's causing problems. Signed-off-by: David Woodhouse --- auth-juniper.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/auth-juniper.c b/auth-juniper.c index 30ceb3ae..f04d49a2 100644 --- a/auth-juniper.c +++ b/auth-juniper.c @@ -188,8 +188,6 @@ static int parse_select_node(struct openconnect_info *vpninfo, struct oc_auth_fo xmlnode_get_prop(node, "name", &opt->form.name); opt->form.label = strdup(opt->form.name); opt->form.type = OC_FORM_OPT_SELECT; - if (!strcmp(opt->form.name, "realm")) - form->authgroup_opt = opt; for (child = node->children; child; child = child->next) { struct oc_choice **new_choices;