Solution to stop unecessary calls to SharePoint Server from Microsoft Office applications

By Namwar Rizvi - Last updated: Saturday, October 8, 2016

Published Links are the addresses of SharePoint sites/libraries which are available to user as a destination to save the document from Office Application. User can add additional sites/libraries by clicking on Connect To Office button on SharePoint Document Library ribbon.

Microsoft Office Applications e.g. Word and Excel try to sync information for all Published Links of SharePoint when a user opens “Save As” dialogue. This call is necessary to ensure that Office application has the latest list of sites which a user has selected by using “Connect to Office” option. Office applications gets the latest list by calling a SharePoint out of the box webservice  available at following server relative address:

/_vti_bin/publishedlinksservice.asmx

Problem:

If Office application unable to access this address, it will display the login prompt. This will quickly become a nuisance, if you no longer use that SharePoint (e.g. you have left organisation, SharePoint address has changed etc.)

Resolution:

Remove the following two Registry entries as follows:

  1. Remove all unncessary sub-keys from HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\15.0\Common\Portal\Link Providers
  2. Remove all unnecessary sub-keys from HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\15.0\Common\Server Links\Published

Above two keys store the SharePoint site addresses to retrieve latest SharePoint locations. Office applications use these registry keys to find SharePoint site addresses and try to connect to SharePoint and shows Sign-in prompts, if unable to connect.

Share
Filed in How To, Information, Solutions, Troubleshooting • Tags: , , , ,

How to receive latest updates in O365 Developer Tenant As Soon As Possible?

By Namwar Rizvi - Last updated: Sunday, September 11, 2016

Microsoft contniously updates Office 365 with new features and experiences and releases them to the users as per release preference selected by customer.

If you have a Developer Tenant account and want to receive updates as soon as possible, you will need to swicth your Release Preference  to First release track.

Following is the step by step procedure to switch the release preference. Please note these action can only be performed by Office 365 Admin. In Developer tenant, you are the Admin 🙂

  1. Sign in to your Office 365 account;
  2. Click Admin tile;
  3. Under Settings, click Organization profile;
  4. Click Release preferences;
  5. In newly opened Release preferences blade, click First release for everyone;
  6. click Next;
  7. Click Yes;
  8. Click Close

 

Share
Filed in How To, Office 365, SharePoint Online • Tags: , , ,

How to enable new User Experience for SharePoint Online Document Libraries and Lists

By Namwar Rizvi - Last updated: Tuesday, July 26, 2016

Microsoft is rolling out new user experience for Document Libraries and Lists in SharePoint Online. If you are a SharePoint Online tenant user and want to test new User Experience for your Document Library and/or SharePoint Lists then perform following steps:

Document Library:

      1. Open Library Settings
      2. Click Advanced Settings
      3. Scroll to bottom of the page, you will see a new setting called List Experience, similar to following:
      4. List Experience Setting
      5. Click New experience
      6. Click OK

SharePoint List:

You can try the same steps for SharePoint Lists also but if they do not work, here is another trick:

  1. Navigate to your desired list
  2. Append a QueryString parameter TryNewExperience=true in your url and refresh the page
  3. Example:
    1. Original List Url: https://yourdomain.sharepoint.com/Lists/Test%20List/AllItems.aspx
    2. After QueryString parameter:  https://yourdomain.sharepoint.com/Lists/Test%20List/AllItems.aspx?TryNewExperience=true
Share
Filed in How To, SharePoint Online • Tags: , , ,

What is a SharePoint Farm?

By Namwar Rizvi - Last updated: Thursday, June 9, 2016

It is a common question asked by many users that what exactly we mean by SharePoint Farm? The answer is

A SharePoint Farm is a collection of all those SharePoint servers that share the same SharePoint configuration database.

By Default, configuration database name is SharePoint_Config. As per Microsoft TechNet article here, configuration database is the fundamental SharePoint database and used for following:

 

Requirements:

Share
Filed in Information • Tags: ,

Step-by-Step SharePoint Online Authentiaction Process via HTTP Protocol

By Namwar Rizvi - Last updated: Monday, March 21, 2016

Here is the step-by-step, behind the scene, authentication process of SharePoint Online. You can use it to connect to SharePoint Online from any Microsoft or Non-Microsoft technology.  It gives you an idea of how things work at the very basic level of HTTP protocol, while authenticating a user in SharePoint Online.

Assumption:

Process:

Note
Replace “yourdomain.com” with your actual domain as registered on sharepoint.com.
Replace “username” with full username e.g. paul.brooks@mycompany.com

  1. Try to access a resource on your SharePoint Online by sending GET e.g.
    1. GET https://yourdomain.sharepoint.com/
    2. Set Header X-IDCRL_ACCEPTED: t
  2. SharePoint Online server will reply with error
    1. 401 Unauthorized along with following header
    2. WWW-Authenticate: IDCRL Type=”BPOSIDCRL”, EndPoint=”/_vti_bin/idcrl.svc/“, RootDomain=”sharepoint.com”, Policy=”MBI”
  3. The above response means, SharePoint Online is challenging you to first authenticate yourself by a trusted AD (Federation Provider) and then come back again, to provided EndPoint (i.e. /_vti_bin/idcrl.svc) , to get authentication Cookie for future session requests.
  4. Now, to get authenticated, you need to send POST request with your username to https://login.microsoftonline.com/getuserrealm.srf?login=username@yourdomain.com&xml=1
  5. SharePoint Online web server will reply with XML similar to following:
 <?xml version="1.0"?><RealmInfo Success="true">  	<State>3</State>  	<UserState>2</UserState>  	<Login>username@yourmain.com</Login>  	<NameSpaceType>Federated</NameSpaceType>  	<DomainName>yourdomain.com</DomainName>  	<FederationGlobalVersion>-1</FederationGlobalVersion>  	<AuthURL>https://sts.yourdomain.com/adfs/ls/</AuthURL>  	<IsFederatedNS>true</IsFederatedNS>  	<STSAuthURL>https://sts.yourdomain.com/adfs/services/trust/2005/usernamemixed</STSAuthURL>  	<FederationTier>0</FederationTier>  	<FederationBrandName>yourdomain.com</FederationBrandName>  	<AllowFedUsersWLIDSignIn>false</AllowFedUsersWLIDSignIn>  	<Certificate>Very Long String Containing your Certificate Information</Certificate>  	<MEXURL>https://sts.yourdomain.com/adfs/services/trust/mex</MEXURL>  	<SAML_AuthURL/>  	<PreferredProtocol>1</PreferredProtocol>  	<EDUDomainFlags>0</EDUDomainFlags>  </RealmInfo>    
  1. Retrieve STSAuthURL value in above XML
  2. POST the following XML to above retrieved STSAuthURL e.g. https://sts.yourdomain.com/adfs/services/trust/2005/usernamemixed
    This will contain your username and password for authentication
 <?xml version="1.0" encoding="UTF-8"?>  <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wssc="http://schemas.xmlsoap.org/ws/2005/02/sc" xmlns:wst="http://schemas.xmlsoap.org/ws/2005/02/trust">  	<s:Header>  		<wsa:Action s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue</wsa:Action>  		<wsa:To s:mustUnderstand="1">https://sts.yourdomain.com/adfs/services/trust/2005/usernamemixed</wsa:To>  		<wsa:MessageID>GUID in this format 7f60eeb9-db69-4411-b600-b6570dfb0ddf</wsa:MessageID>  		<ps:AuthInfo xmlns:ps="http://schemas.microsoft.com/Passport/SoapServices/PPCRL" Id="PPAuthInfo">  			<ps:HostingApp>Managed IDCRL</ps:HostingApp>  			<ps:BinaryVersion>6</ps:BinaryVersion>  			<ps:UIVersion>1</ps:UIVersion>  			<ps:Cookies/>  			<ps:RequestParams>AQAAAAIAAABsYwQAAAAxMDMz</ps:RequestParams>  		</ps:AuthInfo>  		<wsse:Security>  			<wsse:UsernameToken wsu:Id="user">  				<wsse:Username>username@yourdomain.com</wsse:Username>  				<wsse:Password>Password of the user</wsse:Password>  			</wsse:UsernameToken>  			<wsu:Timestamp Id="Timestamp">  				<wsu:Created>2016-03-18T16:26:35.0709397Z</wsu:Created>  				<wsu:Expires>2016-03-18T16:36:35.0719398Z</wsu:Expires>  			</wsu:Timestamp>  		</wsse:Security>  	</s:Header>  	<s:Body>  		<wst:RequestSecurityToken Id="RST0">  			<wst:RequestType>http://schemas.xmlsoap.org/ws/2005/02/trust/Issue</wst:RequestType>  			<wsp:AppliesTo>  				<wsa:EndpointReference>  					<wsa:Address>urn:federation:MicrosoftOnline</wsa:Address>  				</wsa:EndpointReference>  			</wsp:AppliesTo>  			<wst:KeyType>http://schemas.xmlsoap.org/ws/2005/05/identity/NoProofKey</wst:KeyType>  		</wst:RequestSecurityToken>  	</s:Body>  </s:Envelope>  
  1. Server will reply with the following XML, if you have valid username and password. Following contains the SAML security token
  2. You will note that <a:RelatesTo> node contains the same GUID which you passed as MessageID in the Request

 <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">  	<s:Header>  		<a:Action s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/trust/RSTR/Issue</a:Action>  		<a:RelatesTo>7f60eeb9-db69-4411-b600-b6570dfb0ddf</a:RelatesTo>  		<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">  			<u:Timestamp u:Id="_0">  				<u:Created>2016-03-18T16:27:39.529Z</u:Created>  				<u:Expires>2016-03-18T16:32:39.529Z</u:Expires>  			</u:Timestamp>  		</o:Security>  	</s:Header>  	<s:Body>  		<t:RequestSecurityTokenResponse xmlns:t="http://schemas.xmlsoap.org/ws/2005/02/trust">  			<t:Lifetime>  				<wsu:Created xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2016-03-18T16:27:39.523Z</wsu:Created>  				<wsu:Expires xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2016-03-18T17:27:39.523Z</wsu:Expires>  			</t:Lifetime>  			<wsp:AppliesTo xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">  				<wsa:EndpointReference xmlns:wsa="http://www.w3.org/2005/08/addressing">  					<wsa:Address>urn:federation:MicrosoftOnline</wsa:Address>  				</wsa:EndpointReference>  			</wsp:AppliesTo>  			<t:RequestedSecurityToken>  				<saml:Assertion MajorVersion="1" MinorVersion="1" AssertionID="_b73fceb0-XXXX-4f70-98e0-ad664d27afc9" Issuer="http://yourdomain.com/adfs/services/trust/" IssueInstant="2016-03-18T16:27:39.529Z" xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion">  					<saml:Conditions NotBefore="2016-03-18T16:27:39.523Z" NotOnOrAfter="2016-03-18T17:27:39.523Z">  						<saml:AudienceRestrictionCondition>  							<saml:Audience>urn:federation:MicrosoftOnline</saml:Audience>  						</saml:AudienceRestrictionCondition>  					</saml:Conditions>  					<saml:AttributeStatement>  						<saml:Subject>  							<saml:NameIdentifier Format="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified">yFcXXXXC9kS3vGXgpnSyNw==</saml:NameIdentifier>  							<saml:SubjectConfirmation>  								<saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:bearer</saml:ConfirmationMethod>  							</saml:SubjectConfirmation>  						</saml:Subject>  						<saml:Attribute AttributeName="UPN" AttributeNamespace="http://schemas.xmlsoap.org/claims">  							<saml:AttributeValue>username@yourdomain.com</saml:AttributeValue>  						</saml:Attribute>  						<saml:Attribute AttributeName="ImmutableID" AttributeNamespace="http://schemas.microsoft.com/LiveID/Federation/2008/05">  							<saml:AttributeValue>yFcXXXXC9kS3vGXgpnSyNw==</saml:AttributeValue>  						</saml:Attribute>  					</saml:AttributeStatement>  					<saml:AuthenticationStatement AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:password" AuthenticationInstant="2016-03-18T16:27:39.520Z">  						<saml:Subject>  							<saml:NameIdentifier Format="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified">yFcXXXXC9kS3vGXgpnSyNw==</saml:NameIdentifier>  							<saml:SubjectConfirmation>  								<saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:bearer</saml:ConfirmationMethod>  							</saml:SubjectConfirmation>  						</saml:Subject>  					</saml:AuthenticationStatement>  					<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">  						<ds:SignedInfo>  							<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>  							<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>  							<ds:Reference URI="#_b73fceb0-c9e9-XXXX-98e0-ad664d27afc9">  								<ds:Transforms>  									<ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>  									<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>  								</ds:Transforms>  								<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>  								<ds:DigestValue>NK0XXXXapBi+LwTyIXiicj5rfsc=</ds:DigestValue>  							</ds:Reference>  						</ds:SignedInfo>  						<ds:SignatureValue>Very long string as Signature</ds:SignatureValue>  						<KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">  							<X509Data>  								<X509Certificate>Very Long String as Certificate Data</X509Certificate>  							</X509Data>  						</KeyInfo>  					</ds:Signature>  				</saml:Assertion>  			</t:RequestedSecurityToken>  			<t:RequestedAttachedReference>  				<o:SecurityTokenReference k:TokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:k="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd">  					<o:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.0#SAMLAssertionID">_b73XXXX0-c9e9-4f70-98e0-ad664d27afc9</o:KeyIdentifier>  				</o:SecurityTokenReference>  			</t:RequestedAttachedReference>  			<t:RequestedUnattachedReference>  				<o:SecurityTokenReference k:TokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:k="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd">  					<o:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.0#SAMLAssertionID">_b7XXXeb0-c9e9-4f70-98e0-ad664d27afc9</o:KeyIdentifier>  				</o:SecurityTokenReference>  			</t:RequestedUnattachedReference>  			<t:TokenType>urn:oasis:names:tc:SAML:1.0:assertion</t:TokenType>  			<t:RequestType>http://schemas.xmlsoap.org/ws/2005/02/trust/Issue</t:RequestType>  			<t:KeyType>http://schemas.xmlsoap.org/ws/2005/05/identity/NoProofKey</t:KeyType>  		</t:RequestSecurityTokenResponse>  	</s:Body>  </s:Envelope>    
  1. Extract saml:Assertion node from t:RequestedSecurityToken
  2. POST following XML to https://login.microsoftonline.com/RST2.srf
 <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">  	<s:Header>  		<a:Action s:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/trust/RSTR/Issue</a:Action>  		<a:RelatesTo>7f6XXXb9-db69-4411-b600-b6570dfb0ddf</a:RelatesTo>  		<o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">  			<u:Timestamp u:Id="_0">  				<u:Created>2016-03-18T16:27:39.529Z</u:Created>  				<u:Expires>2016-03-18T16:32:39.529Z</u:Expires>  			</u:Timestamp>  		</o:Security>  	</s:Header>  	<s:Body>  		<t:RequestSecurityTokenResponse xmlns:t="http://schemas.xmlsoap.org/ws/2005/02/trust">  			<t:Lifetime>  				<wsu:Created xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2016-03-18T16:27:39.523Z</wsu:Created>  				<wsu:Expires xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2016-03-18T17:27:39.523Z</wsu:Expires>  			</t:Lifetime>  			<wsp:AppliesTo xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">  				<wsa:EndpointReference xmlns:wsa="http://www.w3.org/2005/08/addressing">  					<wsa:Address>urn:federation:MicrosoftOnline</wsa:Address>  				</wsa:EndpointReference>  			</wsp:AppliesTo>  			<t:RequestedSecurityToken>  				<saml:Assertion MajorVersion="1" MinorVersion="1" AssertionID="_b7XXXeb0-c9e9-4f70-98e0-ad664d27afc9" Issuer="http://yourdomain.com/adfs/services/trust/" IssueInstant="2016-03-18T16:27:39.529Z" xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion">  					<saml:Conditions NotBefore="2016-03-18T16:27:39.523Z" NotOnOrAfter="2016-03-18T17:27:39.523Z">  						<saml:AudienceRestrictionCondition>  							<saml:Audience>urn:federation:MicrosoftOnline</saml:Audience>  						</saml:AudienceRestrictionCondition>  					</saml:Conditions>  					<saml:AttributeStatement>  						<saml:Subject>  							<saml:NameIdentifier Format="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified">yFcXXX6C9kS3vGXgpnSyNw==</saml:NameIdentifier>  							<saml:SubjectConfirmation>  								<saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:bearer</saml:ConfirmationMethod>  							</saml:SubjectConfirmation>  						</saml:Subject>  						<saml:Attribute AttributeName="UPN" AttributeNamespace="http://schemas.xmlsoap.org/claims">  							<saml:AttributeValue>username@yourdomain.com</saml:AttributeValue>  						</saml:Attribute>  						<saml:Attribute AttributeName="ImmutableID" AttributeNamespace="http://schemas.microsoft.com/LiveID/Federation/2008/05">  							<saml:AttributeValue>yFcXXXXC9kS3vGXgpnSyNw==</saml:AttributeValue>  						</saml:Attribute>  					</saml:AttributeStatement>  					<saml:AuthenticationStatement AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:password" AuthenticationInstant="2016-03-18T16:27:39.520Z">  						<saml:Subject>  							<saml:NameIdentifier Format="urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified">yFcXXXXC9kS3vGXgpnSyNw==</saml:NameIdentifier>  							<saml:SubjectConfirmation>  								<saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:bearer</saml:ConfirmationMethod>  							</saml:SubjectConfirmation>  						</saml:Subject>  					</saml:AuthenticationStatement>  					<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">  						<ds:SignedInfo>  							<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>  							<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>  							<ds:Reference URI="#_b73XXXb0-c9e9-4f70-98e0-ad664d27afc9">  								<ds:Transforms>  									<ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>  									<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>  								</ds:Transforms>  								<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>  								<ds:DigestValue>NKXXXXsapBi+LwTyIXiicj5rfsc=</ds:DigestValue>  							</ds:Reference>  						</ds:SignedInfo>  						<ds:SignatureValue>Very long string as Signature</ds:SignatureValue>  						<KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#">  							<X509Data>  								<X509Certificate>Very Long String as Certificate Data</X509Certificate>  							</X509Data>  						</KeyInfo>  					</ds:Signature>  				</saml:Assertion>  			</t:RequestedSecurityToken>  			<t:RequestedAttachedReference>  				<o:SecurityTokenReference k:TokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:k="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd">  					<o:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.0#SAMLAssertionID">_b7XXXeb0-c9e9-4f70-98e0-ad664d27afc9</o:KeyIdentifier>  				</o:SecurityTokenReference>  			</t:RequestedAttachedReference>  			<t:RequestedUnattachedReference>  				<o:SecurityTokenReference k:TokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:k="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd">  					<o:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.0#SAMLAssertionID">_b7XXXeb0-c9e9-4f70-98e0-ad664d27afc9</o:KeyIdentifier>  				</o:SecurityTokenReference>  			</t:RequestedUnattachedReference>  			<t:TokenType>urn:oasis:names:tc:SAML:1.0:assertion</t:TokenType>  			<t:RequestType>http://schemas.xmlsoap.org/ws/2005/02/trust/Issue</t:RequestType>  			<t:KeyType>http://schemas.xmlsoap.org/ws/2005/05/identity/NoProofKey</t:KeyType>  		</t:RequestSecurityTokenResponse>  	</s:Body>  </s:Envelope>  
  1. Server Returns following XML and sets following Cookies
    1. SASession=; expires=Thu, 30-Oct-1980 16:00:00 GMT;domain=login.microsoftonline.com;secure= ;path=/;HTTPOnly= ;version=1
    2. x-ms-gateway-slice=orgidprod; path=/; secure; HttpOnly
    3. stsservicecookie=orgidprod; path=/; secure; HttpOnly
    4. Compact Policy token is present. A trailing ‘o’ means opt-out, a trailing ‘i’ means opt-in.
    5. P3P Header is also sent as follows CP=”DSP CUR OTPi IND OTRi ONL FIN”
 <?xml version="1.0" encoding="utf-8" ?>  <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsa="http://www.w3.org/2005/08/addressing">   <S:Header>   <wsa:Action xmlns:S="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Action" S:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2005/02/trust/RSTR/Issue</wsa:Action>   <wsa:To xmlns:S="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="To" S:mustUnderstand="1">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To>   <wsse:Security S:mustUnderstand="1">   <wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="TS">   <wsu:Created>2016-03-18T16:27:40Z</wsu:Created>   <wsu:Expires>2016-03-18T16:32:40Z</wsu:Expires>   </wsu:Timestamp>   </wsse:Security>   </S:Header>   <S:Body>   <wst:RequestSecurityTokenResponse xmlns:S="http://www.w3.org/2003/05/soap-envelope" xmlns:wst="http://schemas.xmlsoap.org/ws/2005/02/trust" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:psf="http://schemas.microsoft.com/Passport/SoapServices/SOAPFault">   <wst:TokenType>urn:passport:compact</wst:TokenType>   <wsp:AppliesTo xmlns:wsa="http://www.w3.org/2005/08/addressing">   <wsa:EndpointReference>   <wsa:Address>sharepoint.com</wsa:Address>   </wsa:EndpointReference>   </wsp:AppliesTo>   <wst:Lifetime>   <wsu:Created>2016-03-18T16:27:40Z</wsu:Created>   <wsu:Expires>2016-03-19T00:27:40Z</wsu:Expires>   </wst:Lifetime>   <wst:RequestedSecurityToken>   <wsse:BinarySecurityToken Id="Compact0">Very Long String to represent Binary Security Token</wsse:BinarySecurityToken>   </wst:RequestedSecurityToken>   <wst:RequestedAttachedReference>   <wsse:SecurityTokenReference>   <wsse:Reference URI="OaBXXXX6kZOe7k9C3MR1SdlN/x0="/>   </wsse:SecurityTokenReference>   </wst:RequestedAttachedReference>   <wst:RequestedUnattachedReference>   <wsse:SecurityTokenReference>   <wsse:Reference URI="OaXXXX46kZOe7k9C3MR1SdlN/x0="/>   </wsse:SecurityTokenReference>   </wst:RequestedUnattachedReference>   </wst:RequestSecurityTokenResponse>   </S:Body>  </S:Envelope>  
  1. Extract the value of
    wsse:BinarySecurityToken [ Id=Compact0 ]

    from above returned XML response

  2. Send following GET request to
    https://yourdomain.sharepoint.com/_vti_bin/idcrl.svc

    after setting following Request Header X-IDCRL_ACCEPTED: t

    1. Authorization: BPOSIDCRL Add the above extracted value of  wsse:BinarySecurityToken [ Id=Compact0 ]
  3. Server will respond to set the special cookie called SPOIDCRL along with P3P policy header. This is the cookie which SharePoint Online will check in all requests, to make sure that your request is coming from an authenticated client. Sample raw response response is as follows:

Buying viagra in amsterdam viagra tablet price india

5 stars based on 151 reviews
I was excited and overzealous and didn’t follow suggestions to start out slowly, buying viagra in amsterdam ending up with a “tomato” red face. The same goes for UHW or indeed any major hospital. Professional treatment of acne begins with a visual examination. Suddenly, I lost the weight that was due to the diabetes, and changed my diet. Impaired secretion of triglycerides by the liver; a cause of tetracycline-induced fatty liver. Sheppard's counsel were present during the three-day inquest but were not permitted to participate.
r viagra 25mg
Farganesse – Kde objednat promethazine bez předpisu. Medicines can be used only with the healthcare provider's supervision. The content on this website is written by a staff of researchers without medical training. The good news is there are effective treatments for anxiety disorders. Ein weiterer Vorteil besteht darin, buy viagra in prague dass Sie in unserer Apotheke Viagra zu günstigen Preisen kaufen können. However, is it legal to buy generic viagra online the trial was small and there was a high level of uncertainty associated with these estimates. This has led us to provide our excellent online pharmacy services to our customers. And don’t be afraid to get more support, finasteride 5 mg o 1 mg like working with a registered dietitian, nutritionist, or therapist. It is used to treat hypertension (high blood pressure), do i need a prescription to get viagra congestive heart failure, and to improve survival after a heart attack. Pharmacokinetic samples were analyzed for lisinopril using a validated analytical method; appropriate pharmacokinetic parameters were calculated for each formulation using non-compartmental methods. In a primarily elderly Scandinavian population, zestril 10 mg price in pakistan the Anglo-Scandinavian Cardiac Outcomes Trial-Blood Pressure Lowering Arm (ASCOT-BPLA) study showed significant overall mortality benefit in subjects aged >60 years when using a combination regimen of calcium channel blocker and ACEI, when compared to a beta-blocker and thiazide regimen. Experiment A-87-39, (b) American Cyanamid Company Report FD 36: (a) Report No. The CYP2D6 isozyme is a common pathway for both of these drugs and norfluoxetine also inhibits this enzyme. Clozapine: (Moderate) Lisinopril may decrease the renal elimination of clozapine and metabolites. But the disadvantage is very serious: ethanol is a weak catalyst of ß-lactam ring disintegration. This substance existed in tissues and secretions like mucus, viagra 200mg tablets tears and egg-white but it did not have much effect on the strongly harmful bacteria. • ^ Kennedy, PG; Rovnak, J; Badani, H; Cohrs, RJ (July 2015). Since PE is associated with personal distress and interrelationship difficulty, dapoxetine provides help for men with PE to overcome this condition. Almost everyone who does laser or Fraxel will advocate prophylaxis for all patients prior to the procedure. Ismania Catherine, Dowager Lady Southampton, is a daughter of Walter Nugent, Esq., a Baron of the Austrian Empire. Its direct indication is to treat herpes infection revealed in different forms in children (older than 12 years) and in adults. If you are being treated for high blood pressure, keep using this medication even if you feel fine. Scottoline B., buying viagra in amsterdam Takase-Sanchez M., Song D., Jegatheesan P., Govindaswami B. Excess water intake is a rare cause of hyponatremia. Cuesta mucho a que se acostumbre la piel al retinoico y si además usas hidroquinona , te aconsejo que seas un poco prudente y si se te irrita demasiado la piel , mejor para uno o dos días . In May I moved up to a new projector, buying viagra in amsterdam a Mitsubishi HC3800 (HD, 1920x1080), and, even though I'm still currently restricted to viewing only a 4:3 aspect ratio image (at lower resolution) with it*, the superior resolution has pushed the (already small) question of "usability" far, far onto the back-burner. Once established, buying viagra in amsterdam the herpes and cold sore virus hides inside a host cell, which makes it difficult for our immune system to recognize and fight. NaCNBH 3 (0.035 g, viagra price in nagpur 0.55 mmol) was added to reaction solution and was monitored by HPLC and LC/MS. Plusieurs facteurs interviennent dans la fréquence et la gravité du bronchospasme: la présence d'éléments allergènes ou irritants dans l'air (poussière, viagra script online cigarette, vapeurs ), la présence de stress ou d'émotions perturbatrices, la fatigue, le froid, l'effort, les rhumes et les grippes. "Questions and answers about sexual anatomy: What is the cul-de-sac?
cost of generic viagra
Hinaus, für andere denken, den gegner brust cancerresearchers entwickeln einen. Daarenboven gaat er dan teveel K + verloren en krijgt men een tekort in de lichaamscellen en dat merkt de patiënt aan spierzwakte en slaapzucht.

• stimulation au 8e jour : 7 jours après l'injection d'ELONVA au premier jour de stimulation, buying viagra in amsterdam la Stimulation ovarienne contrôlée peut être poursuivie par des injections quotidiennes de FSH(rec) jusqu'à ce que le critère de déclenchement de la maturation ovocytaire finale (3 follicules >= 17 mm) soit atteint. Miracle drug for anyone who's deathly afraid of giving speeches or oral presentations. I'd take my Migraine med, buying viagra in amsterdam & it would go away...only to return the next morning! In therapy, buying viagra in amsterdam he finds catharsis and begins to establish trust with his wife, which helps regain a sense of normalcy. It is estimated that nearly 7 percent of healthy elderly persons have serum sodium concentrations of 137 mEq per L or less.

Cialis 20mg vs viagra 50mg


mangel på hvide blodlegemer, buying viagra in amsterdam Øget tendens til blødning pga. These include recommendations that the State Department have a role in evaluating any diplomatic assurances, diclofenaco sodico 50 mg dosis that assurances include a monitoring mechanism in cases in which the assurances are required in order for the transfer to proceed, and that the Offices of the Inspector General at the Departments of State, Defense, and Homeland Security submit a coordinated annual report on all transfers conducted by these agencies. This happens because the blood vessels that bring blood flow to the penis dilate, increasing the blood supply. [15] Addleman challenged this 1997 extension on many grounds, buying viagra in amsterdam including the ISRB's reliance on his litigation history. This presentation is commonly referred to as postinfectious irritable bowel syndrome. No, purchase real viagra and continuing until 1983’s Never Say Never Again. There are no studies yet to support the use of corticosteroids for treating pancreatitis in dogs. Se aconseja precaución al administrar valaciclovir a una mujer en etapa de lactancia. share we communicate more about your article on AOL? This is my first comment here so I just wanted to give a quick shout out and tell you I really enjoy reading your posts. The primary outcome measure was the House–Brackmann grading system for facial-nerve function (see the Supplementary Appendix), com link purchase site viagra 16 an easily administered, widely used clinical system for grading recovery from facial-nerve paralysis caused by damage to lower motor neurons. Tell your doctor: If you are taking any other medicines or herbal remedies, how long viagra 25mg works you have pulmonary tuberculosis (TB), a thyroid problem or a heart problem, or you are having treatment for high blood pressure. Some women choose to view the tissue, buying viagra in amsterdam others are happy not to. Prevention and preemptive therapy of postransplant lymphoproliferative disease in pediatric liver recipients. Whilst many people try and spice up their s ex life by taking drugs, ritonavir viagra online you should only ever take Sildenafil if you are suffering from an inability to get and sustain an erection. Tornata a Londra, where can i buy remeron abbandonò definitivamente il suo appartamento di Coleherne Court per trasferirsi in una suite all'interno di Buckingham Palace, dove studiò il protocollo reale - come parlare in pubblico, salutare e trattare con la servitù. ■ Spread fluid intake throughout the day and reduce it before bedtime, especially coffee, tea, or caffeinated beverages. (Minor) Due to the high protein binding of aspirin, macrodantin 100mg nitrofurantoin it could displace or be displaced from binding sites by other highly protein-bound drugs, such as penicillins.

 

  1. Send this Cookie with all other future SharePoint requests.
Share
Filed in Architecture, Guidance, Information, Security, SharePoint Online, Troubleshooting, Uncategorized • Tags: , , , ,

Quickly find the current used storage of your site collection by using REST

By Namwar Rizvi - Last updated: Wednesday, November 19, 2014

If you want to find out how much storage your SharePoint site collection is currently using then you can use the following REST url in your browser

://<Replace your Site Collection Url>/_api/site/Usage/Storage

For example:

http://sp/_api/site/Usage/Storage

You will get response similar to following. Please note SharePoint report storage in bytes so to get the size in MB you need to divide it by 1048576 .

In following example: storage in MB will be 8038715 / 1048576 = 7.67 MB

 

Storage Size by REST

 

 

Share
Filed in Architecture, Configuration, REST, Solutions, Tips, Troubleshooting • Tags: , , ,

All possible ways to find SharePoint Version and Build number

By Namwar Rizvi - Last updated: Monday, November 3, 2014

If you are trying to find exact Version and Patch level of your SharePoint installation, then use one of the following methods

Method 1 : Using Service.cnf url

  1. Navigate to following url in your browser  <Your SharePoint Site>/_vti_pvt/Service.cnf
  2. You will a response similar to following

vti_encoding:SR|utf8-nl
vti_extenderversion:SR|14.0.0.4762 

Check the number shown in your response at SharePoint Build Numbers

Method 2 : Using Central Administration Site

  1. Launch SharePoint Central Administration site
  2. Under Upgrade and Migration, click Check product and migration status
  3. You will get screen similar to following

Farm Build and Version Number

Method 3 : Using PowerShell

  1. Launch SharePoint 2010 Management Shell
  2. Enter PowerShell command Get-SPFarm | Select BuildVersion
  3. You will get screen similar to following

PowerShellSPFarmBuildNumber

Method 4 : Checking Registry setting

  1. Launch Registry Editor on your SharePoint web front end
  2. Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0
  3. Check the value of BuildVersion as shown in following screen

RegistryVersion

Method 5 : Checking HTTP Header

  1. Launch Fiddler or any other Proxy traffic inspector on any client computer which can access a SharePoint site
  2. Navigate to any page of your SharePoint site on client computer
  3. Check MicrosoftSharePointTeamServices response header in Fiddler, as shown in screen below

Http Header Version

Share
Filed in How To, Installation, PowerShell, Service Pack, SharePoint 2013, SP2010, Tips, Troubleshooting • Tags: , , , , , , , , , , , ,

Solution for “SharePoint Designer cannot display the item” error to edit workflow

By Namwar Rizvi - Last updated: Sunday, November 2, 2014

If you are unable to edit workflows in SharePoint 2013 after upgrading from 2010 and getting following error then perform  the steps mentioned below to resolve this issue.

SharePoint Designer cannot display the item

SharePoint Designer cannot display the item

 

  1. Make sure you have uninstalled SharePoint Designer 2010
  2. Close SharePoint Designer 2013
  3. On the local computer, browse to the following folder:
    • C:\Users\<Replace Your User Name>\AppData\Local\Microsoft\WebsiteCache
    • Example: C:\Users\mark.lee.contoso\AppData\Local\Microsoft\WebsiteCache
  4. Delete everything in WebsiteCache folder.
  5. On the local computer, browse to the following folder:
    • C:\Users\<Replace Your User Name>\AppData\Roaming\Microsoft\SharePoint Designer\ProxyAssemblyCache
    • Example: C:\Users\mark.lee.contoso\AppData\Roaming\Microsoft\SharePoint Designer\ProxyAssemblyCache
  6. Delete everything in ProxyAssemblyCache folder.
  7. Done.
  8. Open SharePoint Designer 2013 and make the changes to your site as needed.

This happens due to cached .NET assemblies in above mentioned folders. These cached files confuses  SPD2013 to use older .NET code which is not compatible with SP2013.

Share
Filed in SharePoint 2013, SharePoint Designer 2013, Solutions, Tips, Troubleshooting, Workflow • Tags: , , ,

Current Item Url in SharePoint Workflow

By Namwar Rizvi - Last updated: Saturday, February 22, 2014

If you want to embed a link to current item in your SharePoint Workflow email or in any other action then use

Workflow Context -> Current Item Url

CurrentItemUrl

 

Share
Filed in Solutions, SP2010, Workflow • Tags: , ,

Exam 70-489 Developing Microsoft SharePoint Server 2013 Advanced Solutions Format

By Namwar Rizvi - Last updated: Sunday, January 19, 2014

If you are preparing for the SharePoint 2013 certification 70-489 i.e. “Developing Microsoft SharePoint Server 2013 Advanced Solutions” then following will be helpful for you with regards to exam format:

For exam content details, skills measured and how to prepare, please refer to the certification page

http://www.microsoft.com/learning/en-us/exam-70-489.aspx

Share
Filed in Certification, Information, SharePoint 2013 • Tags: , ,