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:

Artane 2mg price artane band ireland cost

4 stars based on 197 reviews
La conséquences dispose été à la sorbonne dans le oiseau qui recommence sur la présente d' forme, artane 2mg bula agener partie à l' para-aminophénol nombreuses. Do you need any html coding expertise to make your own blog? It seems like some of the written text on your content are running off the screen. Performing visual retraining exercises at random speeds rather than at specific velocities may be less effective. Since it was banned, a string of athletes across multiple sports have been caught using the drug. For example, when you want to upgrade the disk into a larger one; transfer Windows system or data to other disks.

Artane prescription


http://docs.oasis-open.org/codelist/cs01-ContextValueAssociation-1.0/doc/context-value-association.html. There are other side effects which can be not as serious when taking amoxicillin but you need to still consult your physician if any of these occur. Nuclear localization signals typically are composed of a stretch of basic amino acids. Amitriptyline kan uw reactievermogen beïnvloeden, artane 2mg price met name tijdens de eerste week dat u het middel gebruikt. It was then cooled down to room temperature and was filtered through celite.

Artane 2mg bula indicação


Consider the benefits of breast-feeding, the risk of potential infant drug exposure, and the risk of an untreated or inadequately treated condition. All treatments were well tolerated and were superior to waiting list on nearly all outcome measures; no difference was observed between supportive therapy and waiting list on quality of life. - And many more… You will look at selling in a totally different way that will empower you to be the top go-to-guy/girl in your niche. Nu kan jag prestera utan pillren, men om problem dyker upp kommer jag att bli en återkommande kund. Wenn ich nicht während des Vorhofflimmerns umgefallen wäre wegen Aussetzern des Herzens, artane tablets 2mg jarabe würde ich so ein Medikament mit den Auswirkungen auf die Leber niemals einnehmen. Sometimes the docs are good about writing parameters. • ^ a b "Lady Gaga Tops Forbes' List Of Top-Earning Celebs Under 30". I have lost some of my site from it and no way to sue as the laywers will state its the diabetes. Your participation in the Mann Card Programme is governed by these Mannings' Mann Card Programme Terms and Conditions ("Terms and Conditions"). I en studie utført ved University of Missouri-Columbia, artane 2mg nebenwirkungen 3sat Rusk Rehabilitation Center, og Institutt for fysikalsk medisin og rehabilitering, ble Neurontin brukes for nevropatisk og muskel- og skjelettsmerter på 29 pasienter. In short, Nuance took the “kitchen-sink” approach to adding features. [151] Lady Gaga ha partecipato anche a diversi gay pride: nel 2009 ha preso parte alla National Equality March a Washington, definendola «uno dei momenti più importanti della sua carriera», [152] mentre nel 2011 ha cantato e tenuto un lungo discorso all' Europride di Roma, definendo gli omosessuali dei «rivoluzionari d'amore». When multiple generic companies market a single approved product, artane 2mg price market competition typically results in prices about 85% less than the brand-name. The tet gene in Tn 10 is differentially regulated so that the repressor protein is synthesized before the efflux protein is expressed. Chemotherapy increases the chances of long-term survival and, artane 2 mg 3.0 in most, will extend the quantity and quality of life.

Artane 4 mg xanax


You will find a full list in the manufacturer's information leaflet supplied with your inhaler. Six-Sigma is a data-driven approach and methodology for eliminating defects to achieve six-sigma’s between lower and upper specification limits. The State indicated that it struck veniremember C.J. In the event that we plan to terminate the Mann Card Programme, artane 2mg price we shall give you at least three (3) months notice by display at our Retail Outlets, as well as on the Mann Card Website and/or Mannings Mobile Application or through such other means/channels that Mannings deems appropriate. Fourteen-day optimized levofloxacin-based therapy versus classical quadruple therapy for Helicobacter pylori treatment failures: a randomized clinical trial. In another embodiment, the tetracycline compounds of the invention are essentially non-antibacterial.

Artane side effects 8mg


Reicht preis für dapoxetine 90mg pfizer von dapoxetine wirkung 2015 für radikal verändern. The succinylcholine-induced rise in intraocular pressure (IOP) is minimal (3-8 mm Hg). The MINO (7-dimethylamino-6-demethyl-6-deoxytetracycline) chemical structure contains another dimethylamino group at the C7 on the D ring. Repeated and strong gripping may lead to the condition. To have right treatment and to get the best effectiveness in right time it is recommended to take one pill of Cialis 30 minutes before planned coitus, but in most cases the pill starts its effectiveness in 15 minutes. I have been on the dose for 5 yrs and have had little to no neck and shoulder spasms. «Lady Gaga Bends Gender, artane 2mg price Minds With VMA Monologue» (en inglés). I have heard excellent things about blogengine.net. Cir 2008), artane 2mg price the United States Court of Appeals for the Third Circuit suggested that aliens subject to removal on the basis of diplomatic assurances have the opportunity to present evidence and arguments challenging the reliability of the assurances, and be provided with an individualized determination based on a record disclosed to the alien.

Artane 2mg infarmed


In a further embodiment, the alkynyl R 9 group is substituted with an aminoalkyl group. Witherspoon (1977), indicates that the Navajo have established cultural categories or hierarchies that classify the world based on "potential for motion" (p.140) and acknowledge "air as the source of all knowledge and animation" (p.53). As depression is believed to be caused by neurotransmitters imbalance, it prohibits the reuptake by nerves after they have once been released. (22) Others have struggled with defining the "particular field" or "relevant scientific community" which determines whether the "thing" is generally accepted. Another factor included the fear that Irish women were likely to be or become prostitutes from devastating poverty. Mild reactions may occur in the sensitive individual when the blood alcohol concentration is increased to as little as 5 to 10 mg per 100 mL. The tet(X) gene encodes an enzyme which modifies and inactivates the tetracycline molecule ( 281). see what it would do, and it is quite a powerful mood lifter. Olivia “Sandy” Newton-John was born in England, artane 2.5mg 2.5ml home of Elton John, The Beatles and lots more. Without treatment, artane 2mg price the frequency and severity of symptoms of depression tend to increase over time.

 

  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: , ,