Arkivji ta 'Kull Xahar: Marzu 2009

Pjaċir Fact SharePoint SSO tal-Jum

1 Irrispondi

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. parti web iView). 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, l-utent mhux se jkollhom jidħlu ID tagħhom meta hit up dik is-sistema.

That part worked well for me. Madankollu, dan iqajjem il-kwistjoni, "Kif ma l-utent bidla li id ​​l-utent jew il-password?” The user might have made a mistake, jew forsi inti qed tagħmel xi testijiet f'ambjent DEV u jeħtieġ li jaqilbu malajr bejn il-kontijiet.

I do not know-risposta għal din, imma jien taf li inti tista 'tmur fil Amministrazzjoni Ċentrali u jamministraw kredenzjali tal-utent:

Ċentrali Amministrazzjoni -> Operazzjonijiet -> Manage Uniku Sign-On -> Manage Kont Informazzjoni għal applikazzjoni Definizzjoni Intrapriża

Minn hemm, inti tista 'tispeċifika l-applikazzjoni esterna (e.g. SAP) and the account you want to delete. You can also change the mapping.

Jekk inti taf kif jippermettu lill-utenti finali biex jinbidlu direttament kredenzjali tagħhom, kindly post a comment 🙂

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Avventuri Bil iView Web Parts

Ħalli Risposta

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 ħolqot karta bajda kwalità għolja ħafna fuq dan is-suġġett.

L-ewwel ostaklu kelli biex jingħelbu kien - fejn hija l-parti web iView? Għal xi raġuni, ewwel ħsieb tiegħi kienet li I d jkollhom li tniżżel minn sit x'imkien, perhaps SAP’s site. Kelli 1/2 convinced myself that iView web parts might even cost extra. Of course, huma inklużi ma MOSS (I think Enterprise; dan huwa dak li jien jużaw hawn fi kwalunkwe każ). 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.

I kienet qed tuża l-parti web u miżmuma jkollna dan il-messaġġ annoying:

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

Il-white paper jgħid b'mod ċar li jeditjaw fajl konfigurazzjoni li jinsabu fil-fajl "<Drive Ittra:>\Program Files\Microsoft Office Servers\12.0\Config\TrustedSAPHosts.config”. The first dozen times I looked at that, kollha rajt kien "Program Files ... konfigurazzjoni" u I marru minnufih lill- 12 doqqajs. 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, iżda li storja oħra għal jum ieħor.

Bottom line:

1. web partijiet iView huma inklużi barra mill-kaxxa ma SharePoint (probabbilment Enterprise).

2. Il-fajl konfigurazzjoni magic, "TrustedSAPHosts.config", ma jgħix fil- 12 doqqajs.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

MOSS Profil Utent bħala l-Awtorità għall-preferenza Lingwa User

4 tweġibiet

Fuq il-proġett kurrenti tiegħi, xi wħud mill-utenti ser jivvjaġġaw madwar id-dinja u meta jaslu fid-destinazzjonijiet differenti, use whatever machine is handy at the time. Those guest machines will be running Windows and installed and configured for the local locale. (Stajt biss induna li l-magni mistieden jista 'ma jkollhomx il-lingwa pakketti dritt… probabbilment mhux se, fil-fatt… Jien ipparkjar li wieħed għal issa).

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.

Aħna ser tinvestiga żewġ approċċi:

  1. Handler HTTP: A handler HTTP custom installat fuq IIS se tħares up profil MOSS-utent, insemmu l-lingwa preferita u mbagħad jaqilbu l-header HTTP madwar kif meħtieġ qabel ma jgħaddu kontroll biex 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.

Il-fattur ieħor komplikat huwa li għandna bżonn sabiex l-utenti 60k, dwar 1,000 tagħhom jista 'jkun aċċess simultanjament MOSS b'tagħbija massima.

Il-handler HTTP jidher pjuttost drastiku, 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.

Aħna qed jegħleb lejn approċċ tip global.asax, prinċipalment għaliex aħna nemmnu aħna ser ikollhom aktar għażliet għall-caching data f'dak il-punt.

I ser tkun blogging aktar fuq dan is-suġġett bħala I jitgħallmu aktar.

Jekk għandek tkun taf xejn dwar dan, please post a comment 🙂

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Napprofittaw “mailto:” Metrics

5 tweġibiet

I’m on a project where we need to collect metrics around a function named "Share a Story." The idea is very simple — jekk int tħares lejn artiklu interessanti fuq l-intranet u jridu jaqsmu ma 'xi ħadd, click a link labeled "Share this story" email lill buddy tiegħek.

Aħna lagħbu madwar ma 'formola tad-dwana għal dan il-għan, imma fl-aħħar, sens komun rebaħ il-jum u aħna biss jużaw il-familjari <a href = mailto:…> technique. (<a href mailto:…> huwa ftit sorprendentement robusta ta 'HTML; bħala bonus, dik ir-rabta jwassalni lura għall qodma UNIX tiegħi bniedem jiem paġni; dawk kienu l-jiem!).

Din it-teknika jipprovdi interface kbir għall-utenti finali peress li dawn jiksbu l-użu familjari MS Outlook klijent tagħhom (jew kwalunkwe klijent email li jkunu installati).

Hija tagħmel affarijiet aktar diffiċli fuqna tipi iżviluppatur foqra minħabba li klijent * ukoll * trid tmexxi rapport fil-futur li turi kif spiss stejjer sehem utenti u anke li l-istejjer huma maqsuma aktar spiss.

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. U, we need to manage that event library of emails. We have a scheduled job on the white board responsible for that cleanup.

Jekk għandek xi approċċ għaqlija biex isolvi din il-problema, jekk jogħġbok do tell.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin