getTokenByRangeDate()
getTokenByRangeDate() API returns up to 10,000 tokens created between the specified date range.
Request URL
http://localhost:8080/tmrest/SafeNetTokenManager/getTokenByRangeDate
Method
POST
Request Parameters
| Parameters | Descriptions |
|---|---|
| naeUser | A Key Manager user with access to the AES and HMAC keys. |
| naePassword | The Key Manager user’s password. |
| dbUser (optional) | A database user with access to the token table. |
| dbPassword (optional) | The database user’s password. |
| tableName | This is the Token Vault name and it must be in CAPITAL LETTERS. |
| startDate | The date starting from which the tokens are required. |
| endDate | The date till which the tokens are required. |
| columnToSearch | The particular column which is required as a criterion for searching tokens. Valid value can be either creation date or last accessed date. |
| customData (optional) | The customer-specific data associated with each plaintext value. |
Note
For MySQL, if the customData parameter is null or empty, then the getTokenByRangeDate() API returns results for all the customData values in token vault.
Returned Values
String array of tokens.
Example
{
"naeUser":"user",
"naePassword":"*****",
"dbUser":"sa",
"dbPassword":"xxxxxxxx",
"tableName":"TEST_10",
"startDate":"2014-05-01T08:00:00+0530",
"endDate":"2015-05-01T12:00:00+0530",
"columnToSearch":100
}
Result
{
tokens: [3]
0:"25863143853333"
1:"4302578582222"
2:"6627979014444"
}
