Category Archives: Iter 2009

Fun SharePoint SSO facto Die

1 Respondere

I’ve been working with SharePoint SSO and learning as I go. One way in which this works is that you tell SharePoint about external applications. Users log into that application via some SharePoint function (e.g. iView web part). The first time the user performs this action, it prompts them for the correct user id and password to use for that system. It’s setting up a mapping between your SharePoint credentials and your credentials for that backend system. Thereafter, the user won’t have to enter their ID when they hit up that system.

That part worked well for me. Autem, it begs the question, “how does the user change that user id or password?” The user might have made a mistake, or maybe you’re doing some testing in a dev environment and need to quickly switch between accounts.

I don’t know the answer to that, but I do know that you can go into Central Administration and manage the user’s credentials:

Central Administration –> Operations –> Manage Single Sign-On –> Manage Account Information for an Enterprise Application Definition

From there, you can specify the external application (e.g. SUBRUO) and the account you want to delete. You can also change the mapping.

If you know how to allow end users to directly change their credentials, kindly post a comment 🙂

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Web Partibus Apud serentis iView

Aliquam responsum

I needed to do some minimal proving today that iView web parts can work in my client’s environment. I’ve never worked with this slice of SharePoint before.

Microsoft creavit ipsa princeps qualitas chartam albam DE EODEM.

Primum autem obstaculum superare habui erat - Ubi textus partem iView? Propter aliquam causam,, prima cogitatio mea esset quod debuit download is a site alicubi, perhaps SAP’s site. Habui 1/2 convinced myself that iView web parts might even cost extra. Utique, eae musco (Puto Enterprise; Quoquo hinc usura id quod sum). I’ve seen the standard “add a web part” dialog box hundreds or more times and always glossed over it. No more!

The next obstacle is that I can’t read instructions.

Ego usura est textus huius partis et custodivit molestus nuntius questus:

No SAP servers are configured for this site. Contact your administrator to configure trusted SAP servers.

Dicit paper album plane sit aspernatur in configuration file sita file "<Coegi tabellae:>\Program Files\Microsoft Office Servers\12.0\Config\TrustedSAPHosts.config”. The first dozen times I looked at that, Vidi cuncta erat "Elit Lima ... Config" et ego statim perrexerunt ad 12 alveare. Once I finally slowed down to read it, I realized my mistake and it was easy to fix.

I continued on my merry way with SSO configuration. It’s not all at clear to me if that worked, Est autem alia ratio, quod unum diem.

Imo linea:

1. iView telam partes eae ex arca archa cum SharePoint (Inceptum probabiliter).

2. Magicae configuration file, "TrustedSAPHosts.config", non habitabunt in 12 alveare.

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

User MUSCUS Profile for User auctoritas Language Adumbrationis

4 Restituo

In current consilium meum, Vestibulum Cum ligula lacus et quibusdam aliis propitia perveniunt, use whatever machine is handy at the time. Those guest machines will be running Windows and installed and configured for the local locale. (I’ve just realized that the guest machines may not have the right language packs… probably won’t, in facto… I’m parking that one for now).

SharePoint needs to provide a mechanism whereby the user can pick their preferred language and then have MOSS honor that language regardless of how the user accesses MOSS. In other words, disregard whatever the browser tells IIS/MOSS and instead look up that preferred language and use it.

We’re going to investigate two approaches:

  1. HTTP Handler: A custom HTTP handler installed on IIS will look up the user’s MOSS profile, figure out the preferred language and then switch the HTTP header around as needed before passing control to MOSS.
  2. global.asax: Modify global.asax to do the same thing. We may modify something else, but the idea is that we find some place where we can insert our locale-switching logic.

The other complicating factor is that we need to support 60k users, de 1,000 of which may be simultaneously accessing MOSS at peak load.

The HTTP handler seems pretty drastic, but possibly the best place to put the code since it’s at the IIS level and all-knowing. It’s a good single point of work.

Sumus propensa a typus global.asax adventu, maxime quia credimus puteus 'have magis bene pro puncto illo notitia caching.

Lorem ipsum dolor sit cognoscunt me plura de his blogging.

Si hoc scire aliquid, please post a comment 🙂

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin

Expugnaturum “mailto:” Metrics

5 Restituo

I’m on a project where we need to collect metrics around a function named "Share a Story." The idea is very simple — Si vestri 'vultus in intranet volo ad minim socium elit quis, click a link labeled "Share this story" is ut vestri email Buddy.

Lusimus circum consuetudo forma ad hoc, sed in finem, iustus utor familiaribus et victor sensus <a href = mailto:…> technique. (<a href mailto:…> corpulentiores MIRUM est aliquantulus frenum of HTML; sicut bonus, paginis quibus pagina introduxit me ad virum meum Unix diebus antiquis; diebus illis erant,!).

Hoc ars praebet users cum magna interface pro fine habent usum nota MS Outlook client (vel quidquid email client sunt installed).

Quod facit res duriores nobis cum clienti typos elit, * et páuperem: * in futurum quod vult currere fama ostendit quod etiam saepe users participent fabulis et fabulis plerumque communia sunt.

We whiteboarded a few potential solutions. My favorite is to carbon copy (CC) a SharePoint list. That way, the end user still gets the outlook client while we get to capture the event because we’ll get a copy of the email ourselves. There are some obvious drawbacks. The main problem is that the user could simply blank out or otherwise mangle the CC address. Et, we need to manage that event library of emails. We have a scheduled job on the white board responsible for that cleanup.

Si hoc problema aditum haberent ingenia, dic placeat facere.

</finem>

Scribet ad mea blog.

Sequi me in Twitter ad http://www.twitter.com/pagalvin