Package dev.sigstore.proto.trustroot.v1

Class SigningConfig.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessage.Builder<SigningConfig.Builder>
dev.sigstore.proto.trustroot.v1.SigningConfig.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, SigningConfigOrBuilder, Cloneable
Enclosing class:
SigningConfig
public static final class SigningConfig.Builder extends com.google.protobuf.GeneratedMessage.Builder<SigningConfig.Builder> implements SigningConfigOrBuilder
 SigningConfig represents the trusted entities/state needed by Sigstore
 signing. In particular, it primarily contains service URLs that a Sigstore
 signer may need to connect to for the online aspects of signing.
Protobuf type dev.sigstore.trustroot.v1.SigningConfig

  • Method Details

    • getDescriptor

      public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

    • internalGetFieldAccessorTable

      protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
      Specified by:
      internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessage.Builder<SigningConfig.Builder>

    • clear

      public SigningConfig.Builder clear()
      Specified by:
      clear in interface com.google.protobuf.Message.Builder
      Specified by:
      clear in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clear in class com.google.protobuf.GeneratedMessage.Builder<SigningConfig.Builder>

    • getDescriptorForType

      public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
      Specified by:
      getDescriptorForType in interface com.google.protobuf.Message.Builder
      Specified by:
      getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
      Overrides:
      getDescriptorForType in class com.google.protobuf.GeneratedMessage.Builder<SigningConfig.Builder>

    • getDefaultInstanceForType

      public SigningConfig getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

    • build

      public SigningConfig build()
      Specified by:
      build in interface com.google.protobuf.Message.Builder
      Specified by:
      build in interface com.google.protobuf.MessageLite.Builder

    • buildPartial

      public SigningConfig buildPartial()
      Specified by:
      buildPartial in interface com.google.protobuf.Message.Builder
      Specified by:
      buildPartial in interface com.google.protobuf.MessageLite.Builder

    • mergeFrom

      public SigningConfig.Builder mergeFrom(com.google.protobuf.Message other)
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<SigningConfig.Builder>

    • mergeFrom

      public SigningConfig.Builder mergeFrom(SigningConfig other)

    • isInitialized

      public final boolean isInitialized()
      Specified by:
      isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
      Overrides:
      isInitialized in class com.google.protobuf.GeneratedMessage.Builder<SigningConfig.Builder>

    • mergeFrom

      public SigningConfig.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Specified by:
      mergeFrom in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<SigningConfig.Builder>
      Throws:
      IOException

    • getMediaType

      public String getMediaType()
       MUST be application/vnd.dev.sigstore.signingconfig.v0.2+json
 Clients MAY choose to also support
 application/vnd.dev.sigstore.signingconfig.v0.1+json
      string media_type = 5;
      Specified by:
      getMediaType in interface SigningConfigOrBuilder
      Returns:
      The mediaType.

    • getMediaTypeBytes

      public com.google.protobuf.ByteString getMediaTypeBytes()
       MUST be application/vnd.dev.sigstore.signingconfig.v0.2+json
 Clients MAY choose to also support
 application/vnd.dev.sigstore.signingconfig.v0.1+json
      string media_type = 5;
      Specified by:
      getMediaTypeBytes in interface SigningConfigOrBuilder
      Returns:
      The bytes for mediaType.

    • setMediaType

      public SigningConfig.Builder setMediaType(String value)
       MUST be application/vnd.dev.sigstore.signingconfig.v0.2+json
 Clients MAY choose to also support
 application/vnd.dev.sigstore.signingconfig.v0.1+json
      string media_type = 5;
      Parameters:
      value - The mediaType to set.
      Returns:
      This builder for chaining.

    • clearMediaType

      public SigningConfig.Builder clearMediaType()
       MUST be application/vnd.dev.sigstore.signingconfig.v0.2+json
 Clients MAY choose to also support
 application/vnd.dev.sigstore.signingconfig.v0.1+json
      string media_type = 5;
      Returns:
      This builder for chaining.

    • setMediaTypeBytes

      public SigningConfig.Builder setMediaTypeBytes(com.google.protobuf.ByteString value)
       MUST be application/vnd.dev.sigstore.signingconfig.v0.2+json
 Clients MAY choose to also support
 application/vnd.dev.sigstore.signingconfig.v0.1+json
      string media_type = 5;
      Parameters:
      value - The bytes for mediaType to set.
      Returns:
      This builder for chaining.

    • getCaUrlsList

      public List<Service> getCaUrlsList()
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;
      Specified by:
      getCaUrlsList in interface SigningConfigOrBuilder

    • getCaUrlsCount

      public int getCaUrlsCount()
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;
      Specified by:
      getCaUrlsCount in interface SigningConfigOrBuilder

    • getCaUrls

      public Service getCaUrls(int index)
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;
      Specified by:
      getCaUrls in interface SigningConfigOrBuilder

    • setCaUrls

      public SigningConfig.Builder setCaUrls(int index, Service value)
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;

    • setCaUrls

      public SigningConfig.Builder setCaUrls(int index, Service.Builder builderForValue)
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;

    • addCaUrls

      public SigningConfig.Builder addCaUrls(Service value)
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;

    • addCaUrls

      public SigningConfig.Builder addCaUrls(int index, Service value)
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;

    • addCaUrls

      public SigningConfig.Builder addCaUrls(Service.Builder builderForValue)
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;

    • addCaUrls

      public SigningConfig.Builder addCaUrls(int index, Service.Builder builderForValue)
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;

    • addAllCaUrls

      public SigningConfig.Builder addAllCaUrls(Iterable<? extends Service> values)
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;

    • clearCaUrls

      public SigningConfig.Builder clearCaUrls()
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;

    • removeCaUrls

      public SigningConfig.Builder removeCaUrls(int index)
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;

    • getCaUrlsBuilder

      public Service.Builder getCaUrlsBuilder(int index)
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;

    • getCaUrlsOrBuilder

      public ServiceOrBuilder getCaUrlsOrBuilder(int index)
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;
      Specified by:
      getCaUrlsOrBuilder in interface SigningConfigOrBuilder

    • getCaUrlsOrBuilderList

      public List<? extends ServiceOrBuilder> getCaUrlsOrBuilderList()
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;
      Specified by:
      getCaUrlsOrBuilderList in interface SigningConfigOrBuilder

    • addCaUrlsBuilder

      public Service.Builder addCaUrlsBuilder()
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;

    • addCaUrlsBuilder

      public Service.Builder addCaUrlsBuilder(int index)
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;

    • getCaUrlsBuilderList

      public List<Service.Builder> getCaUrlsBuilderList()
       URLs to Fulcio-compatible CAs, capable of receiving
 Certificate Signing Requests (CSRs) and responding with
 issued certificates.

 These URLs MUST be the "base" URL for the CAs, which clients
 should construct an appropriate CSR endpoint on top of.
 For example, if a CA URL is `https://example.com/ca`, then
 the client MAY construct the CSR endpoint as
 `https://example.com/ca/api/v2/signingCert`.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service ca_urls = 6;

    • getOidcUrlsList

      public List<Service> getOidcUrlsList()
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;
      Specified by:
      getOidcUrlsList in interface SigningConfigOrBuilder

    • getOidcUrlsCount

      public int getOidcUrlsCount()
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;
      Specified by:
      getOidcUrlsCount in interface SigningConfigOrBuilder

    • getOidcUrls

      public Service getOidcUrls(int index)
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;
      Specified by:
      getOidcUrls in interface SigningConfigOrBuilder

    • setOidcUrls

      public SigningConfig.Builder setOidcUrls(int index, Service value)
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;

    • setOidcUrls

      public SigningConfig.Builder setOidcUrls(int index, Service.Builder builderForValue)
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;

    • addOidcUrls

      public SigningConfig.Builder addOidcUrls(Service value)
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;

    • addOidcUrls

      public SigningConfig.Builder addOidcUrls(int index, Service value)
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;

    • addOidcUrls

      public SigningConfig.Builder addOidcUrls(Service.Builder builderForValue)
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;

    • addOidcUrls

      public SigningConfig.Builder addOidcUrls(int index, Service.Builder builderForValue)
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;

    • addAllOidcUrls

      public SigningConfig.Builder addAllOidcUrls(Iterable<? extends Service> values)
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;

    • clearOidcUrls

      public SigningConfig.Builder clearOidcUrls()
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;

    • removeOidcUrls

      public SigningConfig.Builder removeOidcUrls(int index)
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;

    • getOidcUrlsBuilder

      public Service.Builder getOidcUrlsBuilder(int index)
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;

    • getOidcUrlsOrBuilder

      public ServiceOrBuilder getOidcUrlsOrBuilder(int index)
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;
      Specified by:
      getOidcUrlsOrBuilder in interface SigningConfigOrBuilder

    • getOidcUrlsOrBuilderList

      public List<? extends ServiceOrBuilder> getOidcUrlsOrBuilderList()
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;
      Specified by:
      getOidcUrlsOrBuilderList in interface SigningConfigOrBuilder

    • addOidcUrlsBuilder

      public Service.Builder addOidcUrlsBuilder()
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;

    • addOidcUrlsBuilder

      public Service.Builder addOidcUrlsBuilder(int index)
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;

    • getOidcUrlsBuilderList

      public List<Service.Builder> getOidcUrlsBuilderList()
       URLs to OpenID Connect identity providers.

 These URLs MUST be the "base" URLs for the OIDC IdPs, which clients
 should perform well-known OpenID Connect discovery against.

 Clients MUST select only one Service with the highest API version
 that the client is compatible with, that is within its
 validity period, and has the newest validity start date.
 Client SHOULD select the first Service that meets this requirement.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.
      repeated .dev.sigstore.trustroot.v1.Service oidc_urls = 7;

    • getRekorTlogUrlsList

      public List<Service> getRekorTlogUrlsList()
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;
      Specified by:
      getRekorTlogUrlsList in interface SigningConfigOrBuilder

    • getRekorTlogUrlsCount

      public int getRekorTlogUrlsCount()
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;
      Specified by:
      getRekorTlogUrlsCount in interface SigningConfigOrBuilder

    • getRekorTlogUrls

      public Service getRekorTlogUrls(int index)
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;
      Specified by:
      getRekorTlogUrls in interface SigningConfigOrBuilder

    • setRekorTlogUrls

      public SigningConfig.Builder setRekorTlogUrls(int index, Service value)
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;

    • setRekorTlogUrls

      public SigningConfig.Builder setRekorTlogUrls(int index, Service.Builder builderForValue)
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;

    • addRekorTlogUrls

      public SigningConfig.Builder addRekorTlogUrls(Service value)
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;

    • addRekorTlogUrls

      public SigningConfig.Builder addRekorTlogUrls(int index, Service value)
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;

    • addRekorTlogUrls

      public SigningConfig.Builder addRekorTlogUrls(Service.Builder builderForValue)
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;

    • addRekorTlogUrls

      public SigningConfig.Builder addRekorTlogUrls(int index, Service.Builder builderForValue)
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;

    • addAllRekorTlogUrls

      public SigningConfig.Builder addAllRekorTlogUrls(Iterable<? extends Service> values)
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;

    • clearRekorTlogUrls

      public SigningConfig.Builder clearRekorTlogUrls()
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;

    • removeRekorTlogUrls

      public SigningConfig.Builder removeRekorTlogUrls(int index)
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;

    • getRekorTlogUrlsBuilder

      public Service.Builder getRekorTlogUrlsBuilder(int index)
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;

    • getRekorTlogUrlsOrBuilder

      public ServiceOrBuilder getRekorTlogUrlsOrBuilder(int index)
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;
      Specified by:
      getRekorTlogUrlsOrBuilder in interface SigningConfigOrBuilder

    • getRekorTlogUrlsOrBuilderList

      public List<? extends ServiceOrBuilder> getRekorTlogUrlsOrBuilderList()
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;
      Specified by:
      getRekorTlogUrlsOrBuilderList in interface SigningConfigOrBuilder

    • addRekorTlogUrlsBuilder

      public Service.Builder addRekorTlogUrlsBuilder()
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;

    • addRekorTlogUrlsBuilder

      public Service.Builder addRekorTlogUrlsBuilder(int index)
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;

    • getRekorTlogUrlsBuilderList

      public List<Service.Builder> getRekorTlogUrlsBuilderList()
       URLs to Rekor transparency logs.

 These URL MUST be the "base" URLs for the transparency logs,
 which clients should construct appropriate API endpoints on top of.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `rekor_tlog_config`.
      repeated .dev.sigstore.trustroot.v1.Service rekor_tlog_urls = 8;

    • hasRekorTlogConfig

      public boolean hasRekorTlogConfig()
       Specifies how a client should select the set of Rekor transparency
 logs to write to.
      .dev.sigstore.trustroot.v1.ServiceConfiguration rekor_tlog_config = 9;
      Specified by:
      hasRekorTlogConfig in interface SigningConfigOrBuilder
      Returns:
      Whether the rekorTlogConfig field is set.

    • getRekorTlogConfig

      public ServiceConfiguration getRekorTlogConfig()
       Specifies how a client should select the set of Rekor transparency
 logs to write to.
      .dev.sigstore.trustroot.v1.ServiceConfiguration rekor_tlog_config = 9;
      Specified by:
      getRekorTlogConfig in interface SigningConfigOrBuilder
      Returns:
      The rekorTlogConfig.

    • setRekorTlogConfig

      public SigningConfig.Builder setRekorTlogConfig(ServiceConfiguration value)
       Specifies how a client should select the set of Rekor transparency
 logs to write to.
      .dev.sigstore.trustroot.v1.ServiceConfiguration rekor_tlog_config = 9;

    • setRekorTlogConfig

      public SigningConfig.Builder setRekorTlogConfig(ServiceConfiguration.Builder builderForValue)
       Specifies how a client should select the set of Rekor transparency
 logs to write to.
      .dev.sigstore.trustroot.v1.ServiceConfiguration rekor_tlog_config = 9;

    • mergeRekorTlogConfig

      public SigningConfig.Builder mergeRekorTlogConfig(ServiceConfiguration value)
       Specifies how a client should select the set of Rekor transparency
 logs to write to.
      .dev.sigstore.trustroot.v1.ServiceConfiguration rekor_tlog_config = 9;

    • clearRekorTlogConfig

      public SigningConfig.Builder clearRekorTlogConfig()
       Specifies how a client should select the set of Rekor transparency
 logs to write to.
      .dev.sigstore.trustroot.v1.ServiceConfiguration rekor_tlog_config = 9;

    • getRekorTlogConfigBuilder

      public ServiceConfiguration.Builder getRekorTlogConfigBuilder()
       Specifies how a client should select the set of Rekor transparency
 logs to write to.
      .dev.sigstore.trustroot.v1.ServiceConfiguration rekor_tlog_config = 9;

    • getRekorTlogConfigOrBuilder

      public ServiceConfigurationOrBuilder getRekorTlogConfigOrBuilder()
       Specifies how a client should select the set of Rekor transparency
 logs to write to.
      .dev.sigstore.trustroot.v1.ServiceConfiguration rekor_tlog_config = 9;
      Specified by:
      getRekorTlogConfigOrBuilder in interface SigningConfigOrBuilder

    • getTsaUrlsList

      public List<Service> getTsaUrlsList()
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;
      Specified by:
      getTsaUrlsList in interface SigningConfigOrBuilder

    • getTsaUrlsCount

      public int getTsaUrlsCount()
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;
      Specified by:
      getTsaUrlsCount in interface SigningConfigOrBuilder

    • getTsaUrls

      public Service getTsaUrls(int index)
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;
      Specified by:
      getTsaUrls in interface SigningConfigOrBuilder

    • setTsaUrls

      public SigningConfig.Builder setTsaUrls(int index, Service value)
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;

    • setTsaUrls

      public SigningConfig.Builder setTsaUrls(int index, Service.Builder builderForValue)
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;

    • addTsaUrls

      public SigningConfig.Builder addTsaUrls(Service value)
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;

    • addTsaUrls

      public SigningConfig.Builder addTsaUrls(int index, Service value)
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;

    • addTsaUrls

      public SigningConfig.Builder addTsaUrls(Service.Builder builderForValue)
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;

    • addTsaUrls

      public SigningConfig.Builder addTsaUrls(int index, Service.Builder builderForValue)
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;

    • addAllTsaUrls

      public SigningConfig.Builder addAllTsaUrls(Iterable<? extends Service> values)
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;

    • clearTsaUrls

      public SigningConfig.Builder clearTsaUrls()
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;

    • removeTsaUrls

      public SigningConfig.Builder removeTsaUrls(int index)
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;

    • getTsaUrlsBuilder

      public Service.Builder getTsaUrlsBuilder(int index)
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;

    • getTsaUrlsOrBuilder

      public ServiceOrBuilder getTsaUrlsOrBuilder(int index)
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;
      Specified by:
      getTsaUrlsOrBuilder in interface SigningConfigOrBuilder

    • getTsaUrlsOrBuilderList

      public List<? extends ServiceOrBuilder> getTsaUrlsOrBuilderList()
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;
      Specified by:
      getTsaUrlsOrBuilderList in interface SigningConfigOrBuilder

    • addTsaUrlsBuilder

      public Service.Builder addTsaUrlsBuilder()
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;

    • addTsaUrlsBuilder

      public Service.Builder addTsaUrlsBuilder(int index)
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;

    • getTsaUrlsBuilderList

      public List<Service.Builder> getTsaUrlsBuilderList()
       URLs to RFC 3161 Time Stamping Authorities (TSA).

 These URLs MUST be the *full* URL for the TSA, meaning that it
 should be suitable for submitting Time Stamp Requests (TSRs) to
 via HTTP, per RFC 3161.

 Clients MUST group Services by `operator` and select at most one
 Service from each operator. Clients MUST select Services with the
 highest API version that the client is compatible with, that are
 within its validity period, and have the newest validity start dates.
 All listed Services SHOULD be sorted by the `valid_for` window in
 descending order, with the newest instance first.

 Clients MUST select Services based on the selector value of
 `tsa_config`.
      repeated .dev.sigstore.trustroot.v1.Service tsa_urls = 10;

    • hasTsaConfig

      public boolean hasTsaConfig()
       Specifies how a client should select the set of TSAs to request
 signed timestamps from.
      .dev.sigstore.trustroot.v1.ServiceConfiguration tsa_config = 11;
      Specified by:
      hasTsaConfig in interface SigningConfigOrBuilder
      Returns:
      Whether the tsaConfig field is set.

    • getTsaConfig

      public ServiceConfiguration getTsaConfig()
       Specifies how a client should select the set of TSAs to request
 signed timestamps from.
      .dev.sigstore.trustroot.v1.ServiceConfiguration tsa_config = 11;
      Specified by:
      getTsaConfig in interface SigningConfigOrBuilder
      Returns:
      The tsaConfig.

    • setTsaConfig

      public SigningConfig.Builder setTsaConfig(ServiceConfiguration value)
       Specifies how a client should select the set of TSAs to request
 signed timestamps from.
      .dev.sigstore.trustroot.v1.ServiceConfiguration tsa_config = 11;

    • setTsaConfig

      public SigningConfig.Builder setTsaConfig(ServiceConfiguration.Builder builderForValue)
       Specifies how a client should select the set of TSAs to request
 signed timestamps from.
      .dev.sigstore.trustroot.v1.ServiceConfiguration tsa_config = 11;

    • mergeTsaConfig

      public SigningConfig.Builder mergeTsaConfig(ServiceConfiguration value)
       Specifies how a client should select the set of TSAs to request
 signed timestamps from.
      .dev.sigstore.trustroot.v1.ServiceConfiguration tsa_config = 11;

    • clearTsaConfig

      public SigningConfig.Builder clearTsaConfig()
       Specifies how a client should select the set of TSAs to request
 signed timestamps from.
      .dev.sigstore.trustroot.v1.ServiceConfiguration tsa_config = 11;

    • getTsaConfigBuilder

      public ServiceConfiguration.Builder getTsaConfigBuilder()
       Specifies how a client should select the set of TSAs to request
 signed timestamps from.
      .dev.sigstore.trustroot.v1.ServiceConfiguration tsa_config = 11;

    • getTsaConfigOrBuilder

      public ServiceConfigurationOrBuilder getTsaConfigOrBuilder()
       Specifies how a client should select the set of TSAs to request
 signed timestamps from.
      .dev.sigstore.trustroot.v1.ServiceConfiguration tsa_config = 11;
      Specified by:
      getTsaConfigOrBuilder in interface SigningConfigOrBuilder