Authentication Issue in MediaBin:

Selvaraj

Hi,

I have some scripts look something like this:

MediaBinServer service = new MediaBinServer();
Uri u = new Uri("http://****.aspx")
CredentialCache cache = new CredentialCache();
cache.Add( u,"NTLM", new NetworkCredential( strUsername, strPassword, strDomain ));
service.Credentials = cache;
service.PreAuthenticate=false;
service.Url = u.ToString();
service.LockAsset(AssetID,false);

Assuming all the AssetID is valid and the user is an administrator, why is this page working perfectly in a local browser where the MediaBin webservices is installed but it failed when I access this page from a remote browser? the log is throwing an error as access denied

We tried with Basic authencation also but it is throwing the same error.Can you please suggest us what needs to be done for this issue.

Please check with the code.

cache.Add(u, "Basic", New NetworkCredential(MB_UserName, MB_Password, MB_Domain))
MB_service.Credentials = cache
MB_service.Url = u.ToString
'write a line of text to log file
streamWriter.WriteLine(value:="Establish Connection to MediaBin Successful")
streamWriter.WriteLine()

Exception:

System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> MBPNetModel.MBObjects.MBException: MBException: The user is not authorized for the action or access to the object (0x8004041C) at MBPNetModel.MediaBinScriptModel.MediaBinServerImpl .GetAsset(assetID) at MBPNetModel.WebServices.MediaBinServer.GetAsset(assetID) --- End of inner exception stack trace ---

Because of this issue we cant able to make the project live.Please take this issue in high priority and response it ASAP.

msnider

That error message is pretty straight forward. Either the user truly does not have the privilege to lock the asset or the asset has been deleted.

First, double check that the asset has not been deleted. Second, double check that the user is truly an administrator and\or they truly have change permission on the asset.

Also, be aware that since the local case works but the remote case doesn't, it may be an issue with the fact that you are logging in with two different users in both cases...i.e. NTLM\Windows Integrated Authentication is masking the fact that the same user is not being used....double check the MEM audit entries for the login to verify who is logging in and trying to perform the lock.

Mark