This package provides classes necessary to security framework specific for each Wasp instance. It contains provider, current and pstore classes.

ClientSecurityProvider and ServerSecurityProvider define interfaces for authentication provider. Methods setCurrent() on the client side and setCurrentInitiating(), setCurrentAccepting() on the server side perform tasks associated with making security provider active for initiating and accepting new calls. Typically, SecurityProvider adds associating interceptor to stub or service endpoint.

Client and server Current classes enable getting/setting security providers, credentials, authenticators, etc.

PStore classes are a set of interfaces and abstract classes that determine the way to work with protected store. WASP protected store consists of two essential parts KeyStore and UserStore. The key store contains key material for identities. The key store can contain entries for trusted certificates and key entries; i.e., private key and certificate chain. Key entries are intended for use with asymmetric (public) cryptography, SPKM and SSL uses such entries as identities. Trusted certificate entries are there to enable trust based on certificate chains. Trusted certificates must be placed here to tell WASP that they are really trusted. The user store contains security attributes of users, like their passwords and certificates.