Azure的缓存配置编程失败验证 [英] Azure cache programatically configuration fail to verify

问题描述

不知道如果Azure的缓存最近发生了变化，但是访问键似乎有一个稍微不同的格式。

Not sure if Azure cache has recently changed, however the access keys seem to have a slightly different format.

我也跟着从这里的说明：
http://msdn.microsoft.com/en-us/library/windowsazure /gg618003.aspx

I followed the instructions from here: http://msdn.microsoft.com/en-us/library/windowsazure/gg618003.aspx

我设置缓存工厂编程和它的工作原理一种享受。
然而，当我又增加了高速缓存我们的系统，新的高速缓存不起作用。
我得到的错误是：

I setup the cache factory programatically and it works a treat. However, after I added another cache to our system, the new cache doesn't work. The error I get is:

ErrorCode<ERRCA0029>:SubStatus<ES0001>:Authorization token passed by user Invalid.

我以前一样访问高速缓存以同样的方式，唯一的差别是不同的主机和不同的键

I'm accessing the cache in the same way as before, only difference is the different host and the different key.

第一缓存我安装（即工作），具有身份验证令牌是长232个字符。
新的高速缓存具有密钥是只有204。
不知道这是相关的，但我给尽可能多的信息尽可能。

The first cache I setup (that is working), has auth token that is 232 characters long. the new cache has a key that is only 204. Not sure if this is relevant but I'll give as much info as possible.

推荐答案

上的 http://msdn.microsoft.com/en-us/library/windowsazure/gg618003.aspx 是对于具有相同的高速缓存的工作，但与distincts端点。例如添加到您当前缓存HTTPS访问。

The instructions on http://msdn.microsoft.com/en-us/library/windowsazure/gg618003.aspx are for working with the same cache but with distincts endpoints. For example adding https access to your current cache.

如果您希望用2 Azure的缓存工作，只是建立2个不同的对象有2个独立的实现。

If you wish to work with 2 Azure Cache, just build 2 distinct objects with 2 independent implementations.

这篇关于Azure的缓存配置编程失败验证的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！