Set to true if you want to display a tile that links to the static page on the portal home page. Only one of the static pages for a portal can set this flag to true.
Content for the page, markdown in the case of Static pages, url inline_string in the case of Dynamic
PortalSpec
A Portal tells the Gloo Portal operator to fetch and serve static assets which are used by the Gloo Portal UI. Each portal can publish one or more APIProducts.
The domains on which this Portal will be served. The Host header received by the Portal Web App will be matched to one of these domains in order to determine which Portal will be served. If you are using Gloo Edge and the Gateway through which you are exposing the Portal is listening on a port other than 80⁄443, you should include the port as part of the domain string, e.g. “portal.solo.io:8443”. To prevent undefined behavior, creating a Portal whose domain conflicts with an existing Portal or Environment will result in the Portal resource being placed into an ‘Invalid’ state.
This field is required to correctly configure TLS on the VirtualService that is generated by Gloo Portal when enable_ingress is true and you are running in Gloo Edge mode. The field is ignored when running in Istio or Gloo Mesh mode, as TLS is configured by the user on Gatewayor VirtualGateway resources respectively.
Determines which Environments and APIProducts will be published in the Portal. The set of Environments and APIProducts a specific user sees upon login will be filtered by the permissions associated either with that User, or with the Groups that the user is a member of. If the Environments/APIProducts published in the Portal do not intersect with the ones accessible by the User, the user will see no APIProducts.
Controls the behavior of the Portal for users who are not logged in. By default, the Portal requires login to see API Products. If true, all APIs are visible to all users (even those who aren’t logged in).
This field can be used to set arbitrary route options on the route of the generated VirtualService when running in Gloo Edge mode. A fully documented list of the available options can be found in the Gloo Edge documentation here.
Use this field to only publish a subset of the APIProducts included in the Environment. If empty, all APIProducts included in the Environment will be published in the Portal.
Custom labels that will be added to the gateway resources that Gloo Portal generates for this Portal (VirtualServices for Gloo Edge). Any labels that use a reserved key name (e.g. portals.portal.gloo.solo.io/<portalNamespace>.<portalName>) will be ignored.
Reference to a Kubernetes secret containing the OIDC Client Secret to be used to register with the OIDC authentication server. The default key used to look up the secret will be "client_secret" if not specified in the secret ref.
The Key of the OIDC claim containing the names of the Groups which are authorized to access this portal. Portal will check the id_token for the group claim and, if none is found, check the provider’s userinfo for the group claim. The userinfo is retrieved from the userinfo endpoint specified in the provider’s OIDC config as described here: https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfig The group claim is expected to contain one or more group names as either a space-delimited string or an array of strings
The set of Group resources that that all OIDC authenticated users should be considered members of, in addition to the ones specified by the group membership information contained in the ID token. This feature can be used to guarantee a standard set of permissions in cases when the OIDC server cannot include group membership information in the ID tokens it returns to authenticated users.
Any additional scopes to be included in the request. By default, “openid”, “profile”, and “email” are included. As the name indicates, any scopes provided in this field will be included in addition to the defaults, rather than overwriting them. If one of the defaults is provided, it will only be included once.
The text contents of an element to be added to the <head> of all portal pages. Generally, this will be something like a <script> tag. The contents should be valid HTML.
