Struct PingCredentialsProvider 

pub struct PingCredentialsProvider {
    pub ssl_insecure: bool,
    /* private fields */
}

PingFederate identity provider plugin for SAML-based Redshift authentication.

See the Amazon Redshift IAM docs for setup instructions.

Fields

ssl_insecure: bool

When true, TLS certificate verification is disabled. Defaults to false.

Implementations

impl PingCredentialsProvider

pub fn new( partner_sp_id_option: Option<impl ToString>, idp_host: impl ToString, idp_port: Option<u16>, user_name: impl ToString, password: SecretString, ) -> Self

Creates a new PingCredentialsProvider.

• partner_sp_id: The SP entity ID sent to PingFederate. None defaults to "urn%3Aamazon%3Awebservices".
• idp_port: Defaults to 443 when None.

Examples

use secrecy::SecretString;
use redshift_iam::PingCredentialsProvider;

let scp = PingCredentialsProvider::new(
    None::<String>,
    "pingfed.example.com",
    None,
    "alice",
    SecretString::new("s3cr3t".to_string().into_boxed_str()),
);
assert!(!scp.ssl_insecure);
assert!(scp.do_verify_ssl_cert());
assert_eq!(scp.user(), "alice");

pub fn user(&self) -> String

user getter

pub fn do_verify_ssl_cert(&self) -> bool

Returns true when TLS certificate verification is enabled (i.e. ssl_insecure is false).

pub fn get_credentials( &self, preferred_role: impl ToString, ) -> Option<Credentials>

Synchronously retrieves temporary AWS credentials for preferred_role.

Drives the full SAML -> STS flow on a new Tokio runtime. Prefer the async get_credentials free function when already inside an async context.

Trait Implementations

impl Debug for PingCredentialsProvider

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl SamlProvider for PingCredentialsProvider

async fn get_saml_assertion(&self) -> String

Logs in to the PingFederate IdP and returns a base64-encoded SAML assertion.

Issues a GET to the SSO start URL, parses the login form, submits credentials, and extracts the SAMLResponse value from the resulting page.

Panics

• If the login form cannot be parsed or credentials fields are missing.
• If the POST to the IdP returns a non-200 status.
• If no SAMLResponse input is found in the response.