Hello everyone ,
we have morethan one containers in azure blob storgae account.
Assume we have a 3 container
ContainerA,ContainerB,ContainerC
and each continer had saparate access policy interms of expiration date and permission.
Now I will generate the SAS token without using access policy that time I can see "Se" parameter in SAS Token .
If I generate SAS token for individual container using access ploicy i'm not able to see "Se" parameter in SAS token.
please let me know why i'm seeing this deference when i'm creating SAS token .
Thanks
Madan S B
Tuhin PaulPosted Feb 14, 2023, 1:04 PM
The "Se" parameter in a SAS (Shared Access Signature) token stands for "Signed Expiry" and it specifies the expiry time for the SAS token. When you generate a SAS token without using an access policy, you must provide an expiry time explicitly, and this expiry time is included in the "Se" parameter of the token.
On the other hand, when you generate a SAS token using an access policy, the expiry time is specified in the access policy itself, and not in the SAS token. Therefore, the "Se" parameter is not included in the SAS token when using an access policy.
In summary, the reason for the difference in the SAS tokens you generate is that you are explicitly specifying the expiry time when generating a SAS token without using an access policy, whereas the expiry time is specified in the access policy when using one.
Madan ShekarPosted Feb 10, 2023, 10:33 AM
we have start and end time. Se means expiring one right ?