Setting access rights for a BSP Extension

[Former Member]

I was just blindly going through the Help for the WebAS 6.20 looking for how to set security for an application. Setting security for the whole BSP was easy but how/is it possible for setting security for a custom BSP Extension?

We have one application running 3 different BSP Extension (BSPE). The first BSPE is for users A, B and C the second is for users D, E and F and the third is for users A and E????

[former_member181879]

Then you have to program the authority checks yourself into the extension classes. Just do it either in DO_AT_BEGINNING or RUNTIME_VALIDATION (remember to set checkbox that you require validation calls).

[Former Member]

Any good examples for that?

[former_member181879]

help.sap.com/nw04 --> Advanced Search: "authority check"

<a href="http://help.sap.com/saphelp_nw04/helpdata/en/52/67167f439b11d1896f0000e8322d00/frameset.htm">Authorization Checks in Your Own Developments</a>

[Former Member]

Under the nw04 section? I had only been searching under the WebAS 6.20 section. Thanks never would have thought to check there.

I had been doing searching for Security and Access Rights, not once did it occur to me to check for "Authorization"

[former_member181879]

Hallo Craig,

The way SAP is setup, documentation is completed at the end of development, for example at the end of 6.20. However, thereafter the documentation is usually never, or as far as I know, only once or twice, updated again. So the situation is that this documentation is "static". Very much like a printed book.

However, development continues, and often we improve both code and documentation. So, as the development is usually an extension with one cycle building on the next, the newer documentation also applies to the old stuff.

And for BSP this is extreme. We are at the moment still in code sync across all three versions. This is why, especially for us, you should always take the newer documentation. There you benefit from a new update that has been done in the documentation. (Albeit, it is not that much.)

++bcm

[Former Member]

Thinking about it I guess that makes sense, however coming from a Java/PHP background it's a bit strange.

I mean when I am working with JDK version 1.3.1 I look at the API for 1.3.1 and not 1.4.x, however I guess that SAP creates docs for a system and for the tools in the system. Therefore your system is 6.20 but your BSP is using SP 42 so you need the docs and info that go with that which is the newest version of the system ??

Got that right??

[former_member181879]

It is more like documentation is completed in a separate system, and everyone moves on to next release cycle. However, for BSP, because of requirements of big development groups, we were forced to deliver a lot of new functionality into 620. Long after documentation cycle was completed. So 620 documentatiion does not always reflect the full truth.

[Former Member]

Which is then why you recommend ready the nw04 docs then?

[former_member181879]

Yes. As with time, the documentation in our internal systems gets updated. And it is then published again new as nw04 version. Older documentation will probably not be refreshed again. I don't expect that the changes to be dramatical. (And especially for BSP, you already have everything you want in 620.)

[Former Member]

Thanks a bunch, I'll take a look through the docs all again.