GenerallyPositive.IAllowCredentialMethod Interface Reference

The ways a credential can identify itself, which is everything WithService leads to. More...

Inheritance diagram for GenerallyPositive.IAllowCredentialMethod:

Public Member Functions
IAllowCredentialSettings	WithMasterCredentials (ICredentials masterCredentials)
Public Member Functions inherited from GenerallyPositive.IAllowUsernameOrKey
IAllowCredentialsPassword	WithUsername (string username)
IAllowCredentialSettings	WithServiceKey (string key)
IAllowCredentialSettings	WithKeyFromEnv (string envVariableName)
IAllowKeyFromApiEndpoint	WithKeyFromApi (IRESTClient restClient)
Public Member Functions inherited from GenerallyPositive.IAllowToGPALObject< TResult >
TResult	ToGPALObject ()
Public Member Functions inherited from GenerallyPositive.IAllowClientId
IAllowClientSecret	WithClientId (string clientId)
IAllowCredentialSettings	WithServiceAccountKey (GPALFile serviceAccountKeyFile)
IAllowCredentialSettings	WithServiceAccountKey (string serviceAccountKey)
IAllowCredentialSettings	WithServiceAccountKey (GoogleServiceAccountKey serviceAccountKey)

Detailed Description

The ways a credential can identify itself, which is everything WithService leads to.

A vault wants a username and a password. A static key wants the key. An OAuth client wants a client id and secret, and a service account wants its key file. All four follow WithService, so all four are reachable from here, and each narrows to what makes sense after it.

Definition at line 425 of file Interfaces.cs.

Member Function Documentation

WithMasterCredentials()

IAllowCredentialSettings GenerallyPositive.IAllowCredentialMethod.WithMasterCredentials

(

ICredentials

masterCredentials

)

Implemented in GenerallyPositive.Credentials.

---

The documentation for this interface was generated from the following file:

• Common/Interfaces.cs