org.owasp.csrfguard.token.storage

Interface Token

All Known Implementing Classes:

InMemoryToken

public interface Token

TODO

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

Method Detail

getMasterToken

String getMasterToken()

TODO

Returns:

setMasterToken

void setMasterToken(String masterToken)

TODO

Parameters:

masterToken -

getPageToken

String getPageToken(String uri)

TODO

Parameters:

uri -

Returns:

getTimedPageToken

PageTokenValue getTimedPageToken(String uri)

TODO

Parameters:

uri -

Returns:

setPageToken

void setPageToken(String uri,
                  String pageToken)

TODO

Parameters:

uri -

pageToken -

setPageTokenIfAbsent

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

TODO

Parameters:

uri -

valueSupplier -

Returns:

getPageTokens

Map<String,String> getPageTokens()

TODO

Returns:

setPageTokens

void setPageTokens(Map<String,String> pageTokens)

TODO

Parameters:

pageTokens -

rotateAllPageTokens

void rotateAllPageTokens(Supplier<String> tokenValueSupplier)

TODO

Parameters:

tokenValueSupplier -

regenerateUsedPageToken

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.