Skip to content

multiple Google CAS CA mapping with in the config file  #3

Description

@mukeshmohanan

Looking at the configuration it seems the mapping is done to specific CA (using id) in the Google CAS pool , This means if we renew the CA (or wanted to map it to different CA in another region for High availabiltiy)in the then a manual intervention is required to update the new CA id in the json config file and update the CAS gateway before deactivating the old CA.

I could not find a configuration where we can parse a list CA identifier , is this offered ? or I misunderstood the implementation ?

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