org.owasp.csrfguard.token.storage.impl

Class InMemoryToken

java.lang.Object

org.owasp.csrfguard.token.storage.impl.InMemoryToken

All Implemented Interfaces:

Token

public class InMemoryToken
extends Object
implements Token

Constructor Summary

Constructors

Constructor and Description
InMemoryToken(String masterToken)
InMemoryToken(String masterToken, org.apache.commons.lang3.tuple.Pair<String,String> pageToken)

Method Summary

Modifier and Type	Method and Description
String	getMasterToken() TODO
String	getPageToken(String uri) TODO
Map<String,String>	getPageTokens() TODO
PageTokenValue	getTimedPageToken(String uri) TODO
void	regenerateUsedPageToken(String tokenFromRequest, Supplier<String> tokenValueSupplier) TODO is it worth the added performance penalty in case of a large application with a lot of pages? What would be the risk if this would be contextual to the assigned resource? Disposes the current token from all the stored valid page tokens, disregarding to which resource it was assigned and replaces with a newly generated one.
void	rotateAllPageTokens(Supplier<String> tokenValueSupplier) TODO
void	setMasterToken(String masterToken) TODO
void	setPageToken(String uri, String pageToken) TODO
String	setPageTokenIfAbsent(String uri, Supplier<String> valueSupplier) TODO
void	setPageTokens(Map<String,String> pageTokens) TODO

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

InMemoryToken

public InMemoryToken(String masterToken)

InMemoryToken

public InMemoryToken(String masterToken,
                     org.apache.commons.lang3.tuple.Pair<String,String> pageToken)

Method Detail

getMasterToken

public String getMasterToken()

Description copied from interface: Token

TODO

Specified by:

getMasterToken in interface Token

Returns:

setMasterToken

public void setMasterToken(String masterToken)

Description copied from interface: Token

TODO

Specified by:

setMasterToken in interface Token

getPageToken

public String getPageToken(String uri)

Description copied from interface: Token

TODO

Specified by:

getPageToken in interface Token

Returns:

getTimedPageToken

public PageTokenValue getTimedPageToken(String uri)

Description copied from interface: Token

TODO

Specified by:

getTimedPageToken in interface Token

Returns:

setPageToken

public void setPageToken(String uri,
                         String pageToken)

Description copied from interface: Token

TODO

Specified by:

setPageToken in interface Token

setPageTokenIfAbsent

public String setPageTokenIfAbsent(String uri,
                                   Supplier<String> valueSupplier)

Description copied from interface: Token

TODO

Specified by:

setPageTokenIfAbsent in interface Token

Returns:

getPageTokens

public Map<String,String> getPageTokens()

Description copied from interface: Token

TODO

Specified by:

getPageTokens in interface Token

Returns:

setPageTokens

public void setPageTokens(Map<String,String> pageTokens)

Description copied from interface: Token

TODO

Specified by:

setPageTokens in interface Token

rotateAllPageTokens

public void rotateAllPageTokens(Supplier<String> tokenValueSupplier)

Description copied from interface: Token

TODO

Specified by:

rotateAllPageTokens in interface Token

regenerateUsedPageToken

public void regenerateUsedPageToken(String tokenFromRequest,
                                    Supplier<String> tokenValueSupplier)

Description copied from interface: Token

TODO is it worth the added performance penalty in case of a large application with a lot of pages? What would be the risk if this would be contextual to the assigned resource? Disposes the current token from all the stored valid page tokens, disregarding to which resource it was assigned and replaces with a newly generated one.

Specified by:

regenerateUsedPageToken in interface Token