Skip to content

oidcProviders is using Agate internal URL instead of the external one #4553

@thiagomdiniz

Description

@thiagomdiniz

Hi,
In a container-based deployment, services typically communicate using internal names, which are different from external names (usually configured in a reverse proxy).

The problem is that the variable ${oidc.url} is resolving to the internal name of Agate, defined in the Mica configuration file. As in the signin.ftl template:

      <#if oidcProviders?? && oidcProviders?size != 0>
        <div class="social-auth-links text-center mb-3">
          <p>- <@message "sign-in-or"/> -</p>
          <#list oidcProviders as oidc>
            <a href="${oidc.url}" class="btn btn-block btn-primary">
              <@message "sign-in-with"/> ${oidc.title}
            </a>
          </#list>
        </div>
        <!-- /.social-auth-links -->
      </#if>

I believe one solution would be to use the external Agate address that is available through the endpoint /ws/config/_public.

Thanks in advance!

Mica version 6.2.1
Agate version 4.2.7

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions